Triple
T36080619
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Head of Ravenclaw House |
E1043635
|
entity |
| Predicate | holderDuring |
P185376
|
FINISHED |
| Object | Filius Flitwick during Harry Potter’s schooling |
—
|
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: Filius Flitwick during Harry Potter’s schooling | Statement: [Head of Ravenclaw House, holderDuring, Filius Flitwick during Harry Potter’s schooling]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: holderDuring Context triple: [Head of Ravenclaw House, holderDuring, Filius Flitwick during Harry Potter’s schooling]
-
A.
heldAs
Indicates that one entity is kept, maintained, or regarded in a particular state, role, or condition by another entity.
-
B.
holderConducts
Indicates that the holder actively organizes, carries out, or performs the specified event, activity, or process.
-
C.
heldOf
Indicates that something is possessed, controlled, or kept by a particular entity.
-
D.
holderIs
Indicates that one entity serves as the holder, possessor, or container of another entity.
-
E.
ownedDuring
Indicates that one entity possessed or held ownership of another entity for some or all of a specified time interval.
- F. None of above. chosen
Provenance (4 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_69f76e3154908190a6f702671c2bea08 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7be53890081909b1d93f30a8f31c6 |
completed | May 3, 2026, 9:29 p.m. |
| PD | Predicate disambiguation | batch_69f7bccacbac8190978976324c67db28 |
completed | May 3, 2026, 9:23 p.m. |
| PDg | Predicate description generation | batch_69f7be520f148190ba200bf3dbf40656 |
completed | May 3, 2026, 9:29 p.m. |
Created at: May 3, 2026, 4:08 p.m.