Triple
T9467061
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Keepers of the Eastern Door |
E228297
|
entity |
| Predicate | describesFunctionAs |
P264
|
FINISHED |
| Object | easternmost protectors |
—
|
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: easternmost protectors | Statement: [Keepers of the Eastern Door, describesFunctionAs, easternmost protectors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: describesFunctionAs Context triple: [Keepers of the Eastern Door, describesFunctionAs, easternmost protectors]
-
A.
definesFunctioningOf
Indicates that one entity specifies or determines how another entity operates or functions.
-
B.
describes
chosen
Indicates that one entity provides an explanation, representation, or account of another entity or concept.
-
C.
providesFunctionalityOf
Indicates that one entity supplies, implements, or makes available the capabilities or functions that are normally associated with another entity.
-
D.
describedIn
Indicates that information about an entity is contained or documented within a specified source, such as a text, document, or media.
-
E.
intendedFunction
Indicates that something is designed or purposed to perform a particular role, use, or function.
- 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_69ca846fee388190a6ec273fd644b88b |
completed | March 30, 2026, 2:10 p.m. |
| NER | Named-entity recognition | batch_69cd7fdd7d048190930a15cb2a2d99ea |
completed | April 1, 2026, 8:28 p.m. |
| PD | Predicate disambiguation | batch_69cca55f01b081908dc0f12eaa45f832 |
completed | April 1, 2026, 4:55 a.m. |
Created at: March 30, 2026, 7:53 p.m.