Triple
T20078349
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Temple of Janus |
E499929
|
entity |
| Predicate | doorStateInPeace |
P87993
|
FINISHED |
| Object | closed |
—
|
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: closed | Statement: [Temple of Janus, doorStateInPeace, closed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: doorStateInPeace Context triple: [Temple of Janus, doorStateInPeace, closed]
-
A.
doorStateWhen
chosen
Indicates the state or condition of a door at the time when a specified event or situation occurs.
-
B.
doorLevel
Indicates the security or access level required to open or pass through a particular door.
-
C.
doorConfiguration
Indicates how a door is arranged or set up in relation to its frame, opening direction, and operational characteristics.
-
D.
hasDoorGuard
Indicates that an entity has another entity serving as a guard for its door or entrance.
-
E.
doorSafety
Indicates that a door meets specified safety conditions or standards, such as being secure, unobstructed, and compliant with safety regulations.
- 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.