Triple
T20874030
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Inverted Boomerang |
E513969
|
entity |
| Predicate | trackLayoutReuse |
P85513
|
FINISHED |
| Object | train follows same elements in reverse |
—
|
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: train follows same elements in reverse | Statement: [Inverted Boomerang, trackLayoutReuse, train follows same elements in reverse]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trackLayoutReuse Context triple: [Inverted Boomerang, trackLayoutReuse, train follows same elements in reverse]
-
A.
trackLayout
Indicates how the components or segments of a track are arranged and connected in relation to one another.
-
B.
railTracks
Indicates that one entity consists of, includes, or is associated with rail tracks used for guiding trains or rail vehicles.
-
C.
stationLayout
Indicates the spatial arrangement and structural organization of elements within a station.
-
D.
reusesStructureOf
chosen
Indicates that one entity adopts or incorporates the structural design or organization of another entity.
-
E.
infrastructureReuse
Indicates that existing infrastructure is being used again for a new or continued purpose instead of building or deploying entirely new infrastructure.
- 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_69e0b4f675cc8190b4e745225b62eb66 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c46639308190a616193f3975d453 |
completed | April 21, 2026, 12:27 a.m. |
| PD | Predicate disambiguation | batch_69e5c9a8dc148190b33ff51894e2a8f9 |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:45 p.m.