Triple
T24779552
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dalegarth for Boot |
E619952
|
entity |
| Predicate | hasEndOfLineFacilities |
P105786
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Dalegarth for Boot, hasEndOfLineFacilities, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEndOfLineFacilities Context triple: [Dalegarth for Boot, hasEndOfLineFacilities, yes]
-
A.
hasLineCharacter
Indicates that one entity possesses or includes a specific character or symbol that appears within a line of text or sequence.
-
B.
hasLines
Indicates that one entity contains, is composed of, or is associated with one or more linear elements or line segments.
-
C.
hasLineStructure
Indicates that one entity possesses or exhibits a linear arrangement or organization of its components.
-
D.
lineTerminusForSomeServices
chosen
Indicates that a location serves as the endpoint or terminus for at least some, but not necessarily all, of the services operating on a given line.
-
E.
hasIOLines
Indicates that one entity possesses or is associated with one or more input/output (I/O) lines in relation to another 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_69e2fabdbe8c8190adbb9434b8636cad |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f464b4c9b0819085daa00c7c3b8b76 |
completed | May 1, 2026, 8:30 a.m. |
| PD | Predicate disambiguation | batch_69f45cf017a88190b4985b11159c907d |
completed | May 1, 2026, 7:57 a.m. |
Created at: April 18, 2026, 4:43 a.m.