Triple
T5877353
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King’s Commissioner of North Brabant |
E130658
|
entity |
| Predicate | previousTitleUsedUntil |
P64421
|
FINISHED |
| Object | 2013 |
—
|
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: 2013 | Statement: [King’s Commissioner of North Brabant, previousTitleUsedUntil, 2013]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousTitleUsedUntil Context triple: [King’s Commissioner of North Brabant, previousTitleUsedUntil, 2013]
-
A.
previousTitle
Indicates that one title held or used by an entity directly preceded another title in sequence or time.
-
B.
usedAsTitleUntil
chosen
Indicates that a particular title was held or used by an entity up to (and including or until) a specified end time.
-
C.
previousNameUsedUntil
Indicates that a particular name was used for an entity up to (but not necessarily including) a specified end date or time.
-
D.
usedAsTitleBeforeName
Indicates that a term or phrase functions as a formal title placed immediately before a person's name.
-
E.
titleUsedSince
Indicates that a particular title has been in use starting from a specified point in time.
- 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_69c0085523688190bfd487479ce819e6 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c0432fea5881909f5c291dd8db6105 |
completed | March 22, 2026, 7:29 p.m. |
| PD | Predicate disambiguation | batch_69c033499ca08190bd26cee5b03f6306 |
completed | March 22, 2026, 6:22 p.m. |
Created at: March 22, 2026, 3:57 p.m.