Triple
T28518824
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Out-World |
E721699
|
entity |
| Predicate | primaryAssociatedRealm |
P49966
|
FINISHED |
| Object | Mid-World |
—
|
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: Mid-World | Statement: [Out-World, primaryAssociatedRealm, Mid-World]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryAssociatedRealm Context triple: [Out-World, primaryAssociatedRealm, Mid-World]
-
A.
primaryRealm
chosen
Indicates that one entity is the main or principal realm, domain, or sphere of activity associated with another entity.
-
B.
parentRealm
Indicates that one realm serves as the immediate higher-level or containing realm in which another realm is situated.
-
C.
realmAssociatedWith
Indicates an association or connection between an entity and a particular realm, domain, or sphere with which it is linked or to which it pertains.
-
D.
associatedWithRealm
Indicates a relationship where an entity is linked or connected to a particular realm, domain, or sphere of influence.
-
E.
primaryAuthorityFor
Indicates that one entity serves as the main or leading source of control, responsibility, or decision-making power for another entity or domain.
- 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_69f01a5cbcc4819083fb4e723378713e |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_6a0049e40d60819081e3899d8d9fca51 |
completed | May 10, 2026, 9:03 a.m. |
| PD | Predicate disambiguation | batch_6a0048c47b548190ad31b2901cc3784a |
completed | May 10, 2026, 8:58 a.m. |
Created at: April 28, 2026, 3:19 a.m.