Triple
T20361406
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Triwizard Tournament |
E496788
|
entity |
| Predicate | thirdTaskInvolves |
P1256
|
FINISHED |
| Object | navigating a magical maze |
—
|
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: navigating a magical maze | Statement: [Triwizard Tournament, thirdTaskInvolves, navigating a magical maze]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: thirdTaskInvolves Context triple: [Triwizard Tournament, thirdTaskInvolves, navigating a magical maze]
-
A.
involves
chosen
Indicates that an entity participates in, is a part of, or is implicated within a particular event, process, or relationship.
-
B.
thirdFactor
Indicates that an entity serves as the third factor or element in a multi-factor relationship, typically complementing two other primary factors in a given context.
-
C.
thirdWord
Indicates that one entity is the third word in sequence within another entity (such as a text or phrase).
-
D.
targetTask
Indicates that one entity is the specific task or objective that another entity is aiming to perform, achieve, or operate on.
-
E.
involvesWorkers
Indicates that an event, process, or situation includes workers as active participants or affected parties.
- 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_69e0b4a3f7f48190b37f354574028ca6 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6786de5988190827584358c9db147 |
completed | April 20, 2026, 7:03 p.m. |
| PD | Predicate disambiguation | batch_69e57648be3c81908256838228cabf5c |
completed | April 20, 2026, 12:41 a.m. |
Created at: April 16, 2026, 11:25 a.m.