Triple
T1146094
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | JR Yamanote Line |
E23567
|
entity |
| Predicate | loopCompletion |
P1574
|
FINISHED |
| Object | 20th century |
—
|
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: 20th century | Statement: [JR Yamanote Line, loopCompletion, 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: loopCompletion Context triple: [JR Yamanote Line, loopCompletion, 20th century]
-
A.
completionRate
Indicates the proportion of a task, process, or set of items that has been finished relative to its total intended amount.
-
B.
completedIn
chosen
Indicates that an action, process, or task was fully finished within a specified time period or duration.
-
C.
isComplete
Indicates that an action, process, or object has finished all required steps or reached its final state with nothing remaining to be done.
-
D.
closureProcess
Indicates the procedure or set of actions carried out to formally conclude, finalize, or terminate an ongoing activity, case, or process.
-
E.
conversionCompleted
Indicates that a previously initiated conversion process has finished successfully.
- 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_69a493ef399c8190b04b9146d2314f59 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4bc6e8c2081909fb3534413b7aacb |
completed | March 1, 2026, 10:23 p.m. |
| PD | Predicate disambiguation | batch_69a4bb4d4104819084027a043c6118cb |
completed | March 1, 2026, 10:18 p.m. |
Created at: March 1, 2026, 7:44 p.m.