Triple
T9777348
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grey Pilgrim |
E237280
|
entity |
| Predicate | refersToCharacterType |
P60013
|
FINISHED |
| Object | wizard |
—
|
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: wizard | Statement: [Grey Pilgrim, refersToCharacterType, wizard]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: refersToCharacterType Context triple: [Grey Pilgrim, refersToCharacterType, wizard]
-
A.
refersToCharacter
Indicates that one entity makes reference to, mentions, or points to a specific character as its subject.
-
B.
characterCorrespondsTo
Indicates that one character is equivalent to, maps onto, or represents another character in a defined correspondence or mapping.
-
C.
followsCharacterType
Indicates that one character’s behavior, role, or traits are patterned after, derived from, or constrained by a specified character type.
-
D.
typeOfCharacter
chosen
Indicates that one entity is a specific kind or category of character in relation to another entity.
-
E.
relatedCharacterType
Indicates that one character has a specified type of relationship or role in connection to another character.
- 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_69ca84d975a08190aab25b02a89bdab3 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cda133ef548190aaecdf49de9c5aa8 |
completed | April 1, 2026, 10:50 p.m. |
| PD | Predicate disambiguation | batch_69cd03d3b68c81909e570401a891b9f2 |
completed | April 1, 2026, 11:38 a.m. |
Created at: March 30, 2026, 8:26 p.m.