Triple
T9341585
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MUTO |
E224774
|
entity |
| Predicate | organizationInUniverse |
P60680
|
FINISHED |
| Object | monitored by Monarch |
—
|
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: monitored by Monarch | Statement: [MUTO, organizationInUniverse, monitored by Monarch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: organizationInUniverse Context triple: [MUTO, organizationInUniverse, monitored by Monarch]
-
A.
inUniverseOrganization
chosen
Indicates that an organization exists and operates within a specified fictional or narrative universe.
-
B.
associatedUniverse
Indicates that one entity is linked or belongs to a particular universe, realm, or overarching world context.
-
C.
inUniverse
Indicates that one entity exists, occurs, or is set within the fictional or conceptual universe defined by another entity.
-
D.
organizationAssociatedWith
Indicates that there is a formal or recognized connection or affiliation between an organization and another entity.
-
E.
becameUNRelatedOrganization
Indicates that an entity transitioned into having the formal status of a United Nations–related organization.
- F. None of above.
Provenance (3 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_69ca842993248190a79ab06968994b86 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd4bafa9108190889397614756020d |
completed | April 1, 2026, 4:45 p.m. |
| PD | Predicate disambiguation | batch_69cc7a66aef08190b8d668cff5b04f5f |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:40 p.m.