Triple
T28860096
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Texas Giant |
E728835
|
entity |
| Predicate | hasTrackMaterial |
P122237
|
FINISHED |
| Object | steel |
—
|
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: steel | Statement: [New Texas Giant, hasTrackMaterial, steel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTrackMaterial Context triple: [New Texas Giant, hasTrackMaterial, steel]
-
A.
usesTrackMaterial
chosen
Indicates that one entity employs or incorporates a specified track material in its construction, configuration, or operation.
-
B.
hasTrack
Indicates that one entity possesses, includes, or is associated with a specific track (such as a path, course, or recorded item).
-
C.
hasTrackSurface
Indicates that an entity (such as a track) possesses or is characterized by a particular type of surface.
-
D.
hasTrimMaterial
Indicates that one entity uses or features a particular material specifically for its trim or edging components.
-
E.
hasTailTracks
Indicates that an entity exhibits or leaves behind tail-shaped tracks or imprints as evidence of its movement or presence.
- 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_69f031a01cbc8190ba87270bb6fe4639 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69fd884cb2b48190b6acd473430d9e19 |
completed | May 8, 2026, 6:53 a.m. |
| PD | Predicate disambiguation | batch_69fd8709ca208190a8bab836f0156af5 |
completed | May 8, 2026, 6:47 a.m. |
Created at: April 28, 2026, 6:46 a.m.