Triple
T20725403
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rubeus Hagrid |
E509421
|
entity |
| Predicate | escorts |
P33570
|
FINISHED |
| Object | Harry Potter to Diagon Alley |
—
|
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: Harry Potter to Diagon Alley | Statement: [Rubeus Hagrid, escorts, Harry Potter to Diagon Alley]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: escorts Context triple: [Rubeus Hagrid, escorts, Harry Potter to Diagon Alley]
-
A.
numberOfEscorts
Indicates the quantity of escorting entities or units associated with a given entity or event.
-
B.
escortDuty
Indicates that one entity is responsible for accompanying and protecting another entity during travel or movement.
-
C.
escortDuties
chosen
Indicates that one entity is responsible for accompanying and ensuring the safe or guided movement of another entity from one place or situation to another.
-
D.
rendezvousWith
Indicates that two or more entities meet or come together at an agreed place and time, often for a specific purpose.
-
E.
ridesWith
Indicates that one entity is traveling together in the same vehicle or conveyance as another entity.
- 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_69e0b4c4cc648190b45fda6e2b20af56 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c1e7aabc819084f9e9fd45e877fd |
completed | April 21, 2026, 12:16 a.m. |
| PD | Predicate disambiguation | batch_69e5c04b31248190b9b9d91b5cb854e3 |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 12:29 p.m.