Triple
T5111374
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hippogriff |
E115219
|
entity |
| Predicate | canFormBondWith |
P49770
|
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: [Hippogriff, canFormBondWith, wizard]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canFormBondWith Context triple: [Hippogriff, canFormBondWith, wizard]
-
A.
hasBondType
chosen
Indicates the specific kind of bond or connection that exists between two related entities.
-
B.
pairBond
Indicates a long-term, typically exclusive social or reproductive partnership formed between two individuals.
-
C.
canBelongTo
Indicates that something is capable of being a member or part of a particular group, category, or owner.
-
D.
canLiaiseWith
Indicates that one entity is able or permitted to communicate and coordinate directly with another entity for collaboration or information exchange.
-
E.
canCoexistWith
Indicates that two entities are able to exist together in the same context or environment without conflict, interference, or mutual exclusion.
- 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_69bd4441d1648190a54a533895041987 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd75ad362c8190b9cbded390aaea3c |
completed | March 20, 2026, 4:28 p.m. |
| PD | Predicate disambiguation | batch_69bd715fe3a8819087d3065adddba515 |
completed | March 20, 2026, 4:10 p.m. |
Created at: March 20, 2026, 1:41 p.m.