Triple
T31593475
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TNT |
E806161
|
entity |
| Predicate | wasInitiallyUsedAs |
P2417
|
FINISHED |
| Object | yellow dye |
—
|
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: yellow dye | Statement: [TNT, wasInitiallyUsedAs, yellow dye]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasInitiallyUsedAs Context triple: [TNT, wasInitiallyUsedAs, yellow dye]
-
A.
historicallyUsedFor
chosen
Indicates that something served a particular function or purpose at some point in the past, even if it may no longer be used that way now.
-
B.
wasOriginallyBuiltAs
Indicates that an object or structure was initially constructed for a particular purpose, function, or role, which may differ from its current use.
-
C.
formerlyUsedBy
Indicates that an entity was used by another entity in the past but is no longer in use by that entity.
-
D.
usedToBe
Indicates that something held a particular state, role, or property in the past but no longer does in the present.
-
E.
formerPrimaryUse
Indicates that something was previously used as the main or principal function or purpose of an entity, but is no longer its current primary use.
- 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_69f348d4891c8190b02bae3c8ecb68b7 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a8332a008190949520bac1f9a0b0 |
completed | May 3, 2026, 1:43 a.m. |
| PD | Predicate disambiguation | batch_69f6a75656e081908739ed9e2f600e42 |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 30, 2026, 10:29 p.m.