Triple
T37471429
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Temple of Courage |
E931161
|
entity |
| Predicate | covenantZone |
P45917
|
FINISHED |
| Object | Kyrian |
—
|
NE NERFINISHED |
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: Kyrian | Statement: [Temple of Courage, covenantZone, Kyrian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: covenantZone Context triple: [Temple of Courage, covenantZone, Kyrian]
-
A.
covenantLocation
chosen
Indicates the place or setting where a covenant or formal agreement is established, held, or applies.
-
B.
covenantWith
Indicates a formal, binding agreement or promise established between two or more parties.
-
C.
covenantView
Indicates a relationship where one party observes, understands, or interprets the terms, conditions, or implications of a covenant or binding agreement.
-
D.
covenantCommunity
Indicates a relationship in which entities are bound together by a shared covenant, forming a committed, mutually obligated community.
-
E.
covenantAssociation
Indicates a formal, binding relationship or agreement that associates entities under shared obligations, promises, or terms.
- 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_69f76ec2af148190897d101070d7f415 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbacaf54648190811ea33b34907e8e |
completed | May 6, 2026, 9:03 p.m. |
| PD | Predicate disambiguation | batch_69fba883f770819091059c6f6c6af9f7 |
completed | May 6, 2026, 8:45 p.m. |
Created at: May 3, 2026, 4:17 p.m.