Triple
T37720670
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SpX-1 |
E939572
|
entity |
| Predicate | usedTrunkSection |
P189780
|
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: [SpX-1, usedTrunkSection, Yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedTrunkSection Context triple: [SpX-1, usedTrunkSection, Yes]
-
A.
trunkSegments
Indicates that an object is composed of or associated with specific segments of a trunk (such as a tree trunk or similar elongated main structure).
-
B.
usedChassisFor
Indicates that one entity employed or incorporated another entity’s chassis as the structural base or framework for its construction or operation.
-
C.
sharesTrunkWith
Indicates that two entities have a common trunk or main stem from which they both extend or branch.
-
D.
supportsTrunks
Indicates that one entity provides structural or functional support to the trunks of another entity.
-
E.
trunkSymbolizes
Indicates that a trunk (such as that of a tree, elephant, or container) serves as a symbol or representation of some concept, quality, or entity.
- F. None of above. chosen
Provenance (4 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_69f76edc208c8190bc8b9683f75e1024 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbca6c066c8190a1599202f341417f |
completed | May 6, 2026, 11:10 p.m. |
| PD | Predicate disambiguation | batch_69fbc8ee04f08190977b7ad70fc85896 |
completed | May 6, 2026, 11:04 p.m. |
| PDg | Predicate description generation | batch_69fbc993caa881908c16c3e21efaeef9 |
completed | May 6, 2026, 11:07 p.m. |
Created at: May 3, 2026, 4:18 p.m.