Triple
T17908760
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charmcaster |
E447767
|
entity |
| Predicate | relationshipToHex |
P129260
|
FINISHED |
| Object | niece |
—
|
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: niece | Statement: [Charmcaster, relationshipToHex, niece]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipToHex Context triple: [Charmcaster, relationshipToHex, niece]
-
A.
relationshipToUnicode
Indicates a mapping or association between an entity and its corresponding Unicode representation or code point.
-
B.
relationshipToHumans
Indicates the nature or type of connection, association, or relevance that something has specifically with humans.
-
C.
relationshipToWorld
Indicates how an entity is connected or related to the broader world or external environment.
-
D.
hasContrastingRelationshipWith
Indicates a relationship in which two entities are opposed, divergent, or markedly different in qualities, roles, or effects.
-
E.
relationshipToRelative
Indicates the specific familial connection or kinship role that one person has in relation to a particular relative.
- 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_69d8b9f6d394819082a6d69fd1e23d2f |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e49e9e4c9881908bfc3a83809d6b85 |
completed | April 19, 2026, 9:21 a.m. |
| PD | Predicate disambiguation | batch_69e3d8ec2f6881909d7f54b878cbed37 |
completed | April 18, 2026, 7:18 p.m. |
| PDg | Predicate description generation | batch_69e3db77df0c819084548168c62b398c |
completed | April 18, 2026, 7:28 p.m. |
Created at: April 10, 2026, 10:19 a.m.