Triple
T31215998
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wagon Queen Family Truckster |
E795870
|
entity |
| Predicate | propConstructionBase |
P42272
|
FINISHED |
| Object | modified Ford LTD Country Squire |
—
|
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: modified Ford LTD Country Squire | Statement: [Wagon Queen Family Truckster, propConstructionBase, modified Ford LTD Country Squire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: propConstructionBase Context triple: [Wagon Queen Family Truckster, propConstructionBase, modified Ford LTD Country Squire]
-
A.
constructionBase
chosen
Indicates that one entity serves as the foundational structure or base upon which another entity is constructed or built.
-
B.
originalConstructionFor
Indicates that one entity was the initial or first-built structure, design, or form intended for use by another entity.
-
C.
constructionType
Indicates the specific method or style by which something is built or constructed.
-
D.
describesConstructionOf
Indicates that one entity provides information or details about how another entity is built, formed, or constructed.
-
E.
constructionMethod
Indicates the technique or process by which something is built, assembled, or created.
- 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_69f224d9d52c8190a61f68ded37fa755 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69c2b9bd08190ba440c060ebef476 |
completed | May 3, 2026, 12:51 a.m. |
| PD | Predicate disambiguation | batch_69f696673214819094350e1d2648ef34 |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 29, 2026, 9:10 p.m.