Triple
T32074188
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ianus Geminus |
E819097
|
entity |
| Predicate | doorStateMeaning |
P173512
|
FINISHED |
| Object | open doors signify 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 signify war | Statement: [Ianus Geminus, doorStateMeaning, open doors signify war]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: doorStateMeaning Context triple: [Ianus Geminus, doorStateMeaning, open doors signify war]
-
A.
doorStateWhen
Indicates the state or condition of a door at the time when a specified event or situation occurs.
-
B.
doorSymbol
Indicates a symbolic representation that denotes or marks the presence or concept of a door.
-
C.
doorConfiguration
Indicates how a door is arranged or set up in relation to its frame, opening direction, and operational characteristics.
-
D.
doorType
Indicates the specific kind or category of door associated with an entity.
-
E.
doorLevel
Indicates the security or access level required to open or pass through a particular door.
- 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_69f348fecc088190af1470afe5a969f0 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b56ed31481908c3e5d749e46bad9 |
completed | May 3, 2026, 2:39 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a7bdb481908d16a32f49e38c2c |
completed | May 3, 2026, 2:32 a.m. |
| PDg | Predicate description generation | batch_69f6b49339048190b617a6749f648825 |
completed | May 3, 2026, 2:36 a.m. |
Created at: May 1, 2026, 12:23 a.m.