Triple
T26130496
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Enderun Courtyard |
E659230
|
entity |
| Predicate | positionInPalace |
P80879
|
FINISHED |
| Object | third courtyard |
—
|
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: third courtyard | Statement: [Enderun Courtyard, positionInPalace, third courtyard]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionInPalace Context triple: [Enderun Courtyard, positionInPalace, third courtyard]
-
A.
locatedInPalaceSection
chosen
Indicates that one entity is situated within a specific section or area of a palace.
-
B.
positionInRegalia
Indicates the specific role or rank an individual holds within a formal regalia or ceremonial order.
-
C.
positionWithinCastle
Indicates that one entity is located inside the spatial boundaries of a castle.
-
D.
positionInForbiddenCity
Indicates a spatial or locational relationship where an entity is situated at or within a specific place or position inside the Forbidden City.
-
E.
functionRelativeToPalace
Indicates that an entity has a role, purpose, or operational function defined in relation to a specific palace.
- 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_69ee5bc3c20c8190bf2cf272f4170e95 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f6b2a65c7c8190ac40f1466ceadefc |
completed | May 3, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f6b14d7d508190bc7d4c89dfba4a32 |
completed | May 3, 2026, 2:22 a.m. |
Created at: April 26, 2026, 8:14 p.m.