Triple
T8492384
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Foundation versus the Mule |
E201003
|
entity |
| Predicate | involvesPower |
P83016
|
FINISHED |
| Object | mind control |
—
|
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: mind control | Statement: [Foundation versus the Mule, involvesPower, mind control]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: involvesPower Context triple: [Foundation versus the Mule, involvesPower, mind control]
-
A.
involvedPower
Indicates that a particular power, authority, or state is a participant or actor in the referenced event, situation, or relationship.
-
B.
engagedWithPower
Indicates a relationship where an entity actively interacts, collaborates, or aligns with a source of authority, influence, or control.
-
C.
inPowerDuring
Indicates that an entity holds a position of authority or governance throughout a specified time period.
-
D.
invokesPower
Indicates that one entity calls upon, activates, or makes use of the power, authority, or special ability associated with another entity.
-
E.
inPower
Indicates that one entity currently holds governing authority, control, or leadership over a group, organization, or domain.
- 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_69ca831ee390819095fae73400bbfafc |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe55cf5dc81908cad31ac53e15b46 |
completed | March 31, 2026, 3:16 p.m. |
| PD | Predicate disambiguation | batch_69cbd10a4b0881909e254117780dc823 |
completed | March 31, 2026, 1:50 p.m. |
| PDg | Predicate description generation | batch_69cbe30d453481908f897ed2b06e7534 |
completed | March 31, 2026, 3:06 p.m. |
Created at: March 30, 2026, 6:13 p.m.