Triple
T20417251
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sectumsempra |
E500744
|
entity |
| Predicate | knownToBe |
P140060
|
FINISHED |
| Object | unforgivably dangerous for school use |
—
|
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: unforgivably dangerous for school use | Statement: [Sectumsempra, knownToBe, unforgivably dangerous for school use]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: knownToBe Context triple: [Sectumsempra, knownToBe, unforgivably dangerous for school use]
-
A.
knownBefore
Indicates that one entity had knowledge or awareness of another entity or event prior to a specified time or before another referenced event occurred.
-
B.
knownIn
Indicates that an entity is recognized, acknowledged, or familiar within a particular context, domain, or group.
-
C.
knownFrom
Indicates that one entity is aware of, has learned about, or recognizes another entity through a specified source, context, or medium.
-
D.
knownResult
Indicates that the outcome or consequence of an action, process, or event is already determined and available.
-
E.
knows
Indicates that one entity has knowledge or awareness of another entity or piece of information.
- 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_69e0b4a935588190b9446a99b37ced44 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e67a44ecf48190ba5a3872af500dc8 |
completed | April 20, 2026, 7:11 p.m. |
| PD | Predicate disambiguation | batch_69e5766df0008190a73c4f613c29678f |
completed | April 20, 2026, 12:42 a.m. |
| PDg | Predicate description generation | batch_69e58d766b408190a1d3698145fb6d30 |
completed | April 20, 2026, 2:20 a.m. |
Created at: April 16, 2026, 11:30 a.m.