Triple
T29893576
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | the Empire |
E759217
|
entity |
| Predicate | enforcer |
P128619
|
FINISHED |
| Object | Darth Vader |
—
|
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: Darth Vader | Statement: [the Empire, enforcer, Darth Vader]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: enforcer Context triple: [the Empire, enforcer, Darth Vader]
-
A.
enforcement
Indicates the act of compelling compliance with rules, laws, or agreements through monitoring, pressure, or sanctions.
-
B.
disciplinarianOf
Indicates that one entity holds and exercises strict authority or control over another, enforcing rules and discipline.
-
C.
enforcementModel
Indicates the method or framework by which rules, policies, or constraints are applied, monitored, and enforced within a system or interaction.
-
D.
enforcesLawThrough
chosen
Indicates that one entity upholds, applies, or executes laws or legal rules by means of another entity, mechanism, or process.
-
E.
defender
Indicates a relationship where one entity protects, guards, or supports another entity against threats, attacks, or criticism.
- 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_69f2245f1cf88190978c70d1a1d2cb73 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f67729a7ac8190b99cf3fcc0e2c60c |
completed | May 2, 2026, 10:14 p.m. |
| PD | Predicate disambiguation | batch_69f66ec8298c8190b41fe9d182c05676 |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 29, 2026, 6:03 p.m.