Triple
T18520881
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USRA stock car |
E452578
|
entity |
| Predicate | designedToHaul |
P18005
|
FINISHED |
| Object | cattle |
—
|
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: cattle | Statement: [USRA stock car, designedToHaul, cattle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designedToHaul Context triple: [USRA stock car, designedToHaul, cattle]
-
A.
shipDesigned
Indicates that one entity is responsible for designing or creating the design of a ship associated with another entity.
-
B.
designedToEmbark
Indicates that something is created or configured with the specific purpose of beginning or initiating a journey, process, or undertaking.
-
C.
hauls
chosen
Indicates that one entity pulls, drags, or transports another entity, typically involving effort or force over a distance.
-
D.
shipRig
Indicates that one entity is equipped with or configured using the rigging system specified by another entity.
-
E.
shipCompanion
Indicates that one entity serves as a companion or partner accompanying another entity on a ship or sea voyage.
- 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_69d8d386df84819092355ebb260d848e |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5338db5e4819086503a2176dfe499 |
completed | April 19, 2026, 7:57 p.m. |
| PD | Predicate disambiguation | batch_69e469e0025c81908f16ed4f922674af |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:37 a.m.