Triple
T9559922
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Smoke |
E230641
|
entity |
| Predicate | hasKeySign |
P9766
|
FINISHED |
| Object | a visible smoke covering people |
—
|
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: a visible smoke covering people | Statement: [The Smoke, hasKeySign, a visible smoke covering people]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasKeySign Context triple: [The Smoke, hasKeySign, a visible smoke covering people]
-
A.
hasSign
chosen
Indicates that an entity possesses, displays, or is associated with a particular sign or symbol.
-
B.
hasSignFor
Indicates that one entity displays, bears, or provides a sign, symbol, or notice that represents, directs attention to, or gives information about another entity.
-
C.
hasKeyPass
Indicates that an entity possesses or is granted a key-based pass that allows access or authorization to something.
-
D.
hasSignaturePhrase
Indicates that an entity (such as a person or character) is associated with a distinctive, repeatedly used phrase that is characteristically theirs.
-
E.
hasKeyDua
Indicates that one entity possesses or is associated with a specific secondary or backup key related to another entity.
- 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_69ca847e53a88190a60eed7e02257f10 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd994bde0c8190afcba5cb8fa8b984 |
completed | April 1, 2026, 10:16 p.m. |
| PD | Predicate disambiguation | batch_69ccd594d0ac8190a81bc11a3a538167 |
completed | April 1, 2026, 8:21 a.m. |
Created at: March 30, 2026, 8:03 p.m.