Triple
T31105000
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hayt |
E792769
|
entity |
| Predicate | hasPlanImposedBy |
P187388
|
FINISHED |
| Object | Bene Tleilax |
—
|
NE NERFINISHED |
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: Bene Tleilax | Statement: [Hayt, hasPlanImposedBy, Bene Tleilax]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPlanImposedBy Context triple: [Hayt, hasPlanImposedBy, Bene Tleilax]
-
A.
hasPlan
Indicates that an entity possesses or is associated with a specific plan or course of action.
-
B.
hasPlanningConstraint
Indicates that there is a rule, limitation, or condition that must be considered when planning or scheduling an activity, resource, or process.
-
C.
hadRestrictionsOn
Indicates that one entity imposed or was subject to specific limitations, rules, or constraints regarding another entity or activity.
-
D.
hasTypicalPlan
Indicates that there is a standard or commonly followed plan, procedure, or course of action typically associated with the given entity or situation.
-
E.
hasBasePlan
Indicates that an entity is associated with or derived from a specified foundational or default plan.
- 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_69f224cfd5d881908ec6447bc321cd58 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fb563aec448190875410fb1a3ed624 |
completed | May 6, 2026, 2:54 p.m. |
| PD | Predicate disambiguation | batch_69fb35b9ede881908aaae93a215525df |
completed | May 6, 2026, 12:36 p.m. |
| PDg | Predicate description generation | batch_69fb563a28d88190b28345c465c545f8 |
completed | May 6, 2026, 2:54 p.m. |
Created at: April 29, 2026, 9:03 p.m.