Triple
T36569560
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Keita Goto |
E902077
|
entity |
| Predicate | typeOfOrganizationFounded |
P8556
|
FINISHED |
| Object | private railway company |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: private railway company | Statement: [Keita Goto, typeOfOrganizationFounded, private railway company]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfOrganizationFounded Context triple: [Keita Goto, typeOfOrganizationFounded, private railway company]
-
A.
organizationTypeFounded
chosen
Indicates the type or category of organization that was established or created in a founding event.
-
B.
foundedOrganizationType
Indicates that an entity established or created an organization of a specified type (e.g., company, nonprofit, institution).
-
C.
inceptionOfOrganization
Indicates that an event, action, or point in time marks the founding or formal beginning of an organization.
-
D.
foundedOrganization
Indicates that an entity established or created an organization.
-
E.
organizationFoundedAs
Indicates that an organization was originally established under a particular name, form, or predecessor entity.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69f76e6416708190a9754b8c52d4e453 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a0316136a14819085bb88563d5abc42 |
completed | May 12, 2026, 11:59 a.m. |
| PD | Predicate disambiguation | batch_6a03158a962c81909f17d58197f6ba00 |
completed | May 12, 2026, 11:56 a.m. |
Created at: May 3, 2026, 4:11 p.m.