Triple
T28518820
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Out-World |
E721699
|
entity |
| Predicate | relationToMid-World |
P201667
|
FINISHED |
| Object | associated realm |
—
|
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: associated realm | Statement: [Out-World, relationToMid-World, associated realm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationToMid-World Context triple: [Out-World, relationToMid-World, associated realm]
-
A.
relationshipToRelative
Indicates the specific familial connection or kinship role that one person has in relation to a particular relative.
-
B.
relationshipToHumans
Indicates the nature or type of connection, association, or relevance that something has specifically with humans.
-
C.
relationToBabo
Indicates a relationship or connection that an entity has to the person or entity referred to as "Babo."
-
D.
relationToVonMaur
Indicates a specified type of relationship or association that an entity has with Von Maur.
-
E.
relationshipToCharacter
Indicates the specific type of personal, social, or narrative connection that one entity has to a given character.
- 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_69f01a5cbcc4819083fb4e723378713e |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_6a00119d821c8190874786391b27ef23 |
completed | May 10, 2026, 5:03 a.m. |
| PD | Predicate disambiguation | batch_6a001143fb6881909ac0ae8bfea04351 |
completed | May 10, 2026, 5:01 a.m. |
| PDg | Predicate description generation | batch_6a00119ca1d881909a72a9c3b937c43c |
completed | May 10, 2026, 5:03 a.m. |
Created at: April 28, 2026, 3:19 a.m.