Triple
T9308302
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Temple of Janus Geminus (probable) |
E223942
|
entity |
| Predicate | doorStateWhen |
P87993
|
FINISHED |
| Object | doors open during 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: doors open during war | Statement: [Temple of Janus Geminus (probable), doorStateWhen, doors open during war]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: doorStateWhen Context triple: [Temple of Janus Geminus (probable), doorStateWhen, doors open during war]
-
A.
doorConfiguration
Indicates how a door is arranged or set up in relation to its frame, opening direction, and operational characteristics.
-
B.
doorLevel
Indicates the security or access level required to open or pass through a particular door.
-
C.
doorType
Indicates the specific kind or category of door associated with an entity.
-
D.
hasDoor
Indicates that one entity possesses or is equipped with a door that provides access to or through it.
-
E.
doorLocation
Indicates the spatial position or placement of a door relative to a reference structure or area.
- 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_69ca8424d0f08190831e2e93c6533aeb |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd1daa21188190b1b2e508b0d09dcb |
completed | April 1, 2026, 1:29 p.m. |
| PD | Predicate disambiguation | batch_69cc7a61e9a4819096eb014f3791ef2e |
completed | April 1, 2026, 1:52 a.m. |
| PDg | Predicate description generation | batch_69cc955a38108190b602d1e73725f11b |
completed | April 1, 2026, 3:47 a.m. |
Created at: March 30, 2026, 7:37 p.m.