Triple
T29342116
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sheriff Little |
E744062
|
entity |
| Predicate | relationshipWithDukes |
P203143
|
FINISHED |
| Object | adversarial but occasionally cooperative |
—
|
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: adversarial but occasionally cooperative | Statement: [Sheriff Little, relationshipWithDukes, adversarial but occasionally cooperative]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipWithDukes Context triple: [Sheriff Little, relationshipWithDukes, adversarial but occasionally cooperative]
-
A.
recognizedAsDuke
Indicates that an entity is formally acknowledged or accepted as holding the title or status of a duke.
-
B.
establishedAsDukes
Indicates that certain individuals or entities were formally created or recognized with the rank and title of dukes.
-
C.
relationshipToHenry
Indicates the specific type of relationship or connection that an entity has to Henry.
-
D.
relationshipToDukeSenior
Indicates that one entity holds a specified familial or social relationship to an older or higher-ranking duke.
-
E.
relationshipToPrincess
Indicates the specific familial, social, or romantic connection that one entity has to a princess.
- 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_69f09126cfcc8190899b16fbf3c2bf7b |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_6a01289f781481908f3788f8a719f2f4 |
completed | May 11, 2026, 12:53 a.m. |
| PD | Predicate disambiguation | batch_6a012823c7248190961e20be48dd6246 |
completed | May 11, 2026, 12:51 a.m. |
| PDg | Predicate description generation | batch_6a01289ecf7481908802642bb4399ac0 |
completed | May 11, 2026, 12:53 a.m. |
Created at: April 28, 2026, 1:34 p.m.