Triple
T8442926
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Đoan Môn Gate |
E199591
|
entity |
| Predicate | roleInCitadel |
P83391
|
FINISHED |
| Object | main access point to central royal area |
—
|
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: main access point to central royal area | Statement: [Đoan Môn Gate, roleInCitadel, main access point to central royal area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInCitadel Context triple: [Đoan Môn Gate, roleInCitadel, main access point to central royal area]
-
A.
roleInElysium
Indicates that an entity holds a specific role, position, or function within the context of Elysium.
-
B.
roleInSyriana
Indicates that one entity has a specific role or involvement in the context of "Syriana," such as participation, function, or contribution related to it.
-
C.
deFactoRole
Indicates that an entity effectively functions in a role or capacity in practice, even if that role is not formally or officially assigned.
-
D.
roleInCreed
Indicates that an entity holds a specific role or function within a particular creed, doctrine, or belief system.
-
E.
roleInBladeII
Indicates that an entity has a specific role or participation in the movie "Blade II."
- 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_69ca83170f9081909cd98f55614c6476 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe310d8e08190b871bda79acde678 |
completed | March 31, 2026, 3:06 p.m. |
| PD | Predicate disambiguation | batch_69cbd0f5a3648190beb53a139a2d5482 |
completed | March 31, 2026, 1:49 p.m. |
| PDg | Predicate description generation | batch_69cbe30c2d088190b4cb89adb4e88273 |
completed | March 31, 2026, 3:06 p.m. |
Created at: March 30, 2026, 6:08 p.m.