Triple
T37957821
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A-09 |
E946914
|
entity |
| Predicate | identifiesLine |
P189666
|
FINISHED |
| Object | IND Eighth Avenue Line |
—
|
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: IND Eighth Avenue Line | Statement: [A-09, identifiesLine, IND Eighth Avenue Line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: identifiesLine Context triple: [A-09, identifiesLine, IND Eighth Avenue Line]
-
A.
definedLine
Indicates that a specific line (such as a boundary, path, or reference line) has been formally established or specified within a given context.
-
B.
isLinedWith
Indicates that one object or surface is covered, edged, or internally coated along its length or area with another material or layer.
-
C.
hasLineDescribing
Indicates that one entity includes or provides a line of text that describes or characterizes another entity.
-
D.
accessibleForLine
Indicates that something (such as a resource, area, or facility) can be reached, used, or served by a particular line (e.g., a transport or service line).
-
E.
testingLine
Indicates that one entity is being used as a test or trial version of a line, sequence, or boundary associated with another entity.
- F. None of above. chosen
Provenance (4 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_69f76ef64cf08190ad3e1114b62aac67 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbc7b78f9481909f4f8fc2e3fdcde1 |
completed | May 6, 2026, 10:59 p.m. |
| PD | Predicate disambiguation | batch_69fbbd18c9908190928d274f8731dfa8 |
completed | May 6, 2026, 10:13 p.m. |
| PDg | Predicate description generation | batch_69fbc7b6c2c88190ad4f58980834053c |
completed | May 6, 2026, 10:59 p.m. |
Created at: May 3, 2026, 4:20 p.m.