Triple
T16114236
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | court of Louis XIII |
E390961
|
entity |
| Predicate | hasCourtOffice |
P19057
|
FINISHED |
| Object | First Minister of State |
—
|
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: First Minister of State | Statement: [court of Louis XIII, hasCourtOffice, First Minister of State]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCourtOffice Context triple: [court of Louis XIII, hasCourtOffice, First Minister of State]
-
A.
hasCourts
Indicates that an entity possesses, contains, or is equipped with one or more courts (e.g., legal, sports, or judicial facilities).
-
B.
hasCourthouse
Indicates that a location or jurisdiction possesses or contains a courthouse.
-
C.
hasCourtroomsFor
Indicates that an entity provides or contains courtrooms designated for use by another entity or purpose.
-
D.
hasCourtDivision
Indicates that a court is organized into, or belongs to, a specific internal division or section within the judicial system.
-
E.
hasAssociatedOffice
chosen
Indicates that an entity is linked to or connected with a particular office in an official or functional capacity.
- 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_69d87f1a8dd881909f1de6ef78849874 |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e20169ce488190bbc814f23a3b7547 |
completed | April 17, 2026, 9:46 a.m. |
| PD | Predicate disambiguation | batch_69e1828518c48190a8ef3aaa46a1f639 |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 5 a.m.