Triple
T28813721
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 名神高速道路 |
E727581
|
entity |
| Predicate | 旧管理者 |
P12937
|
FINISHED |
| Object | 日本道路公団 |
—
|
NE NERFINISHED |
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: 日本道路公団 | Statement: [名神高速道路, 旧管理者, 日本道路公団]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 旧管理者 Context triple: [名神高速道路, 旧管理者, 日本道路公団]
-
A.
previousAdministrator
chosen
Indicates that one entity formerly held an administrative role or position over another entity before the current administrator.
-
B.
previousMaintainer
Indicates that one entity formerly held responsibility for maintaining another entity before the current maintainer.
-
C.
formerManagingCompany
Indicates that one entity previously served as the managing company responsible for overseeing or operating another entity, but no longer holds that role.
-
D.
formerAdministeredBy
Indicates that an entity was previously administered or managed by another entity, but is no longer under that administration.
-
E.
foundingManager
Indicates that an entity serves as the original or initial manager responsible for establishing or setting up another entity (such as an organization, project, or initiative).
- 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_69f0319c38948190bca746ad60fd25ba |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f658f163a88190b1dd222eaa0f93ea |
completed | May 2, 2026, 8:05 p.m. |
| PD | Predicate disambiguation | batch_69f65762b5e481908a30ca963dcba4be |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 6:32 a.m.