Triple
T20005348
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lumen Industries |
E494442
|
entity |
| Predicate | hasCorporateSymbolism |
P129
|
FINISHED |
| Object | goats on severed floor |
—
|
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: goats on severed floor | Statement: [Lumen Industries, hasCorporateSymbolism, goats on severed floor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCorporateSymbolism Context triple: [Lumen Industries, hasCorporateSymbolism, goats on severed floor]
-
A.
emblemSymbolism
Indicates that one entity serves as an emblem whose design or features symbolically represent or convey meanings about another entity.
-
B.
haveOfficialSymbols
Indicates that an entity possesses formally recognized symbols (such as flags, emblems, or insignia) that officially represent it.
-
C.
symbolizes
chosen
Indicates that one entity stands for, represents, or is used as a sign for another entity, concept, or idea.
-
D.
symbolizedIn
Indicates that one entity serves as a symbol or representation of another entity.
-
E.
symbolismIn
Indicates that one entity functions as a symbol or representation within the context, meaning, or interpretive framework of 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_69da626b2d748190886981ea90c8b2ea |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e661a46c748190a141ab5aac6ea250 |
completed | April 20, 2026, 5:25 p.m. |
| PD | Predicate disambiguation | batch_69e54cdddbd48190becc8b2aa5ab4ef9 |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 3:33 p.m.