Triple
T19265390
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tiers État |
E481761
|
entity |
| Predicate | positionInEstatesSystem |
P92324
|
FINISHED |
| Object | third estate |
—
|
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: third estate | Statement: [Tiers État, positionInEstatesSystem, third estate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionInEstatesSystem Context triple: [Tiers État, positionInEstatesSystem, third estate]
-
A.
positionEstablishedIn
Indicates the point in time or event when a particular position, role, or office was formally created or instituted.
-
B.
positionOnEstablishment
Indicates the spatial or functional placement of one entity relative to an establishment (such as being located on, within, or as part of that establishment).
-
C.
propertyLocation
Indicates the geographical place or address where a property is situated or found.
-
D.
positionInSettlement
Indicates the specific location or placement of an entity within the boundaries or layout of a settlement.
-
E.
positionEstablishedUnder
chosen
Indicates that a position or role was created or formally instituted according to the authority, rules, or framework of a specified governing body, document, or system.
- 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_69d8e8ce54cc8190998418ff1f66ef28 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fb8ca2e88190baad3b6c199ee036 |
completed | April 20, 2026, 10:10 a.m. |
| PD | Predicate disambiguation | batch_69e4dd07a7208190afcd51ba1dc87c33 |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:29 p.m.