Triple
T30344420
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amestris |
E771834
|
entity |
| Predicate | hasConspiracy |
P112937
|
FINISHED |
| Object | Homunculi control of government |
—
|
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: Homunculi control of government | Statement: [Amestris, hasConspiracy, Homunculi control of government]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasConspiracy Context triple: [Amestris, hasConspiracy, Homunculi control of government]
-
A.
conspiracy
chosen
Indicates a secret agreement or collaboration between multiple entities to plan or carry out an unlawful, deceptive, or harmful act.
-
B.
conspiracyType
Indicates the specific category or nature of a conspiracy associated with an entity or event.
-
C.
hasApproximateNumberOfConspirators
Indicates that an entity is associated with an estimated or approximate count of conspirators involved with it.
-
D.
deathConspiracy
Indicates a relationship where one party is involved in planning, supporting, or believing in a covert plot to cause another party’s death.
-
E.
conspirator
Indicates that an entity participates with others in planning or carrying out a secret or illicit scheme or 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_69f2248b9a208190bc3e6804acd5afd6 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a0136e4af808190b529d324bbf0c5d9 |
completed | May 11, 2026, 1:54 a.m. |
| PD | Predicate disambiguation | batch_6a01369141c4819091cb8064913a44ca |
completed | May 11, 2026, 1:53 a.m. |
Created at: April 29, 2026, 7:55 p.m.