Triple
T32855135
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Court of Louis XVI of France |
E840355
|
entity |
| Predicate | governedByCode |
P202345
|
FINISHED |
| Object | Versailles court etiquette |
—
|
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: Versailles court etiquette | Statement: [Court of Louis XVI of France, governedByCode, Versailles court etiquette]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governedByCode Context triple: [Court of Louis XVI of France, governedByCode, Versailles court etiquette]
-
A.
governedFor
Indicates that one entity exercised governing authority or administrative control on behalf of, or in the interest of, another entity.
-
B.
hasGovernorateCode
Indicates that an entity is associated with a specific governorate through a designated code.
-
C.
governedByAct
Indicates that something is regulated, controlled, or legally defined by a specific act or piece of legislation.
-
D.
governedWith
Indicates that two or more entities share or participate together in the act or process of governing.
-
E.
governedInPartBy
Indicates that something is subject to the authority, control, or influence of a governing entity, but only to a limited or partial extent rather than fully.
- 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_69f349412c78819084459850e11d29f7 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a0075be7f54819081ab12bc1dab53bb |
completed | May 10, 2026, 12:10 p.m. |
| PD | Predicate disambiguation | batch_6a0073a19030819098c23faa3adcb96e |
completed | May 10, 2026, 12:01 p.m. |
| PDg | Predicate description generation | batch_6a0075bd35e08190b604777ae9fbbe4b |
completed | May 10, 2026, 12:10 p.m. |
Created at: May 1, 2026, 1:17 a.m.