Triple
T20078331
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Temple of Janus |
E499929
|
entity |
| Predicate | symbolicMeaningOfDoors |
P124062
|
FINISHED |
| Object | open doors signified Rome at war |
—
|
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: open doors signified Rome at war | Statement: [Temple of Janus, symbolicMeaningOfDoors, open doors signified Rome at war]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: symbolicMeaningOfDoors Context triple: [Temple of Janus, symbolicMeaningOfDoors, open doors signified Rome at war]
-
A.
doorSymbol
Indicates a symbolic representation that denotes or marks the presence or concept of a door.
-
B.
shapeSymbolism
Indicates how a particular shape is associated with or conveys symbolic meaning within a given context.
-
C.
starMeaning
Indicates that one entity represents or conveys the symbolic or interpretive significance of a star associated with another entity.
-
D.
dreamsSignified
Indicates that one entity’s dreams symbolically represent, foreshadow, or convey information about another entity or situation.
-
E.
objectMeaning
chosen
Indicates that one entity represents, expresses, or conveys the meaning or semantic content 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_69da627770948190997f486f9a2e370f |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e6643e216c819088c002fc1de2772a |
completed | April 20, 2026, 5:37 p.m. |
| PD | Predicate disambiguation | batch_69e54cf369b88190931532420517dac7 |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 3:40 p.m.