Triple
T20210347
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Witherwings |
E493471
|
entity |
| Predicate | legalStatusDuringAlias |
P139211
|
FINISHED |
| Object | fugitive creature |
—
|
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: fugitive creature | Statement: [Witherwings, legalStatusDuringAlias, fugitive creature]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legalStatusDuringAlias Context triple: [Witherwings, legalStatusDuringAlias, fugitive creature]
-
A.
legalStatusAfterRenaming
Indicates the legal status or classification that applies to an entity after it has undergone a renaming.
-
B.
legalStatusAtIssue
Indicates that the legal status of an entity is the central subject of dispute, consideration, or determination in a legal context.
-
C.
legalStatusBefore
Indicates the legal condition or classification that applied to an entity prior to a specified event, change, or point in time.
-
D.
legalStatusChangedIn
Indicates that an entity’s legal status was altered or reclassified within a specified jurisdiction, context, or time frame.
-
E.
legalStatusAfterEvent
Indicates the legal condition or classification an entity has as a result of a specified event or occurrence.
- 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_69da6269614c8190bb40475d9d477358 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e66ed4706c81908a5e4a3023a9c22f |
completed | April 20, 2026, 6:22 p.m. |
| PD | Predicate disambiguation | batch_69e55b14c9d8819095453d0504d9222f |
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:38 p.m.