Triple
T33083045
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Genoshan government |
E846557
|
entity |
| Predicate | policyOnMutants |
P94281
|
FINISHED |
| Object | mutant registration |
—
|
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: mutant registration | Statement: [Genoshan government, policyOnMutants, mutant registration]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: policyOnMutants Context triple: [Genoshan government, policyOnMutants, mutant registration]
-
A.
policyVariation
Indicates that one policy differs from another in certain terms, conditions, or parameters.
-
B.
policyShift
Indicates a change or adjustment in an existing policy, typically reflecting a new direction, priority, or approach.
-
C.
policySetBy
chosen
Indicates that a particular policy is established, defined, or determined by a specific entity or authority.
-
D.
publicPolicy
Indicates that an entity is a government or institutional rule, principle, or course of action intended to address public issues or guide societal outcomes.
-
E.
policyResponseTo
Indicates a relationship where a policy is created, modified, or applied as a direct reaction to a specific event, condition, or prior action.
- 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_69f34954d46c8190a04a159cc5f99efd |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f78fd5a6388190bfda4bbb2e222e5b |
completed | May 3, 2026, 6:11 p.m. |
| PD | Predicate disambiguation | batch_69f78e2ac3fc819081a45c6841375c8d |
completed | May 3, 2026, 6:04 p.m. |
Created at: May 1, 2026, 1:26 a.m.