Triple
T5111411
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marauder's Map |
E115220
|
entity |
| Predicate | deactivationPhrase |
P61648
|
FINISHED |
| Object | Mischief managed |
—
|
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: Mischief managed | Statement: [Marauder's Map, deactivationPhrase, Mischief managed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deactivationPhrase Context triple: [Marauder's Map, deactivationPhrase, Mischief managed]
-
A.
deactivated
Indicates that an entity has been turned off, disabled, or rendered inactive so it no longer performs its usual function or role.
-
B.
inactivationReason
Indicates the reason or cause for which an entity, status, or process has been deactivated or made inactive.
-
C.
ceasedActivityUnder
Indicates that an entity stopped performing a particular activity while under the authority, influence, or conditions imposed by another entity.
-
D.
renouncedBy
Indicates that an entity has been formally rejected, disowned, or given up by another entity.
-
E.
suspensionDate
Indicates the date on which an entity’s normal status, operation, or privileges are formally suspended.
- 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_69bd4441d1648190a54a533895041987 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd75ca57e881908242def2a032902e |
completed | March 20, 2026, 4:28 p.m. |
| PD | Predicate disambiguation | batch_69bd715fe3a8819087d3065adddba515 |
completed | March 20, 2026, 4:10 p.m. |
| PDg | Predicate description generation | batch_69bd72e1b7cc8190b2e621fdf8f22e38 |
completed | March 20, 2026, 4:16 p.m. |
Created at: March 20, 2026, 1:41 p.m.