Triple
T20186634
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Extendable Ears |
E492877
|
entity |
| Predicate | usedToOverhear |
P139028
|
FINISHED |
| Object | Order of the Phoenix meetings at 12 Grimmauld Place |
—
|
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: Order of the Phoenix meetings at 12 Grimmauld Place | Statement: [Extendable Ears, usedToOverhear, Order of the Phoenix meetings at 12 Grimmauld Place]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedToOverhear Context triple: [Extendable Ears, usedToOverhear, Order of the Phoenix meetings at 12 Grimmauld Place]
-
A.
heardBy
Indicates that a sound, message, or communication produced by one entity is perceived or received auditorily by another entity.
-
B.
hearsFrom
Indicates that one entity receives information, communication, or a message from another entity.
-
C.
heard
Indicates that one entity perceived a sound produced by another entity or source through hearing.
-
D.
hears
Indicates that one entity perceives or detects sounds produced by another entity or source.
-
E.
mayHear
Indicates that one entity is permitted or able to hear sounds, speech, or audio produced by another entity.
- 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_69da6268a034819081cbd9ea5a1c9475 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e66ad143c48190b9d52c331e8101d6 |
completed | April 20, 2026, 6:05 p.m. |
| PD | Predicate disambiguation | batch_69e55b11124c8190babacf2a0fe2d057 |
completed | April 19, 2026, 10:45 p.m. |
| PDg | Predicate description generation | batch_69e56700b1a08190ace53cf95827d72d |
completed | April 19, 2026, 11:36 p.m. |
Created at: April 11, 2026, 11:36 p.m.