Triple
T37241124
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Imperial Knights |
E923713
|
entity |
| Predicate | didNotHave |
P38071
|
FINISHED |
| Object | seat in the Imperial Diet |
—
|
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: seat in the Imperial Diet | Statement: [Imperial Knights, didNotHave, seat in the Imperial Diet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: didNotHave Context triple: [Imperial Knights, didNotHave, seat in the Imperial Diet]
-
A.
didNotHold
Indicates that an expected event, condition, or relationship failed to occur or be valid.
-
B.
hadNo
chosen
Indicates that one entity completely lacked or did not possess another entity, attribute, or relationship.
-
C.
doesNotHave
Indicates that one entity lacks, is missing, or is not in possession of another entity or attribute.
-
D.
didNotBecome
Indicates that an expected or potential change of state, role, or condition between entities did not occur.
-
E.
didNotReturnTo
Indicates that an entity failed or chose not to go back to a previous place, state, or situation after having left it.
- 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_69f76ea9fee88190a589f661d95a7189 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb4134225081909fd60703b8cae397 |
completed | May 6, 2026, 1:25 p.m. |
| PD | Predicate disambiguation | batch_69fb35bf767081908de8345358ca7f44 |
completed | May 6, 2026, 12:36 p.m. |
Created at: May 3, 2026, 4:15 p.m.