Triple
T5128340
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harry Potter |
E115634
|
entity |
| Predicate | triwizardTaskStatus |
P54268
|
FINISHED |
| Object | co-winner with Cedric Diggory |
—
|
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: co-winner with Cedric Diggory | Statement: [Harry Potter, triwizardTaskStatus, co-winner with Cedric Diggory]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: triwizardTaskStatus Context triple: [Harry Potter, triwizardTaskStatus, co-winner with Cedric Diggory]
-
A.
tourStatus
Indicates the current state or phase of a tour within its overall lifecycle (e.g., planned, active, completed, or canceled).
-
B.
trainingStatus
Indicates the current state or phase of an entity within a training or learning process.
-
C.
statusOfObjectivesResolution
Indicates the relationship that specifies how and to what extent defined objectives have been resolved or achieved.
-
D.
participantStatus
chosen
Indicates the role, condition, or level of involvement that a participant has within a specific event, process, or relationship.
-
E.
scriptoriumStatus
Indicates the current operational or functional state of a scriptorium within a given context.
- 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_69bd444426bc819099ccd23f141e22aa |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd7d5a23908190a24e79d1b29d6fcf |
completed | March 20, 2026, 5:01 p.m. |
| PD | Predicate disambiguation | batch_69bd77aa68b88190a50dd736a72d2901 |
completed | March 20, 2026, 4:36 p.m. |
Created at: March 20, 2026, 1:42 p.m.