Triple
T31479186
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mézières |
E803088
|
entity |
| Predicate | capitalStatusUntil |
P71730
|
FINISHED |
| Object | 1966 |
—
|
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: 1966 | Statement: [Mézières, capitalStatusUntil, 1966]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: capitalStatusUntil Context triple: [Mézières, capitalStatusUntil, 1966]
-
A.
capitalStatusStart
Indicates the point in time when a place first acquires its status as a capital.
-
B.
legalStatusEnd
chosen
Indicates the point or event at which a previously valid legal status, condition, or arrangement ceases to be in effect.
-
C.
designationStatus
Indicates the current official classification or standing assigned to an entity within a defined system or process.
-
D.
capitalPreviouslyAt
Indicates that an entity once served as the capital of another entity in the past, but no longer holds that status.
-
E.
capitalLaterAt
Indicates that one entity becomes the capital of another entity at a later point in time than a referenced capital or event.
- 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_69f348c9477c8190bc0a21f6d482d2fc |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fce7671f108190bf3ebf54339068b5 |
completed | May 7, 2026, 7:26 p.m. |
| PD | Predicate disambiguation | batch_69fce5b5a84c81908ac1b5b9f08d48d0 |
completed | May 7, 2026, 7:19 p.m. |
Created at: April 30, 2026, 9:31 p.m.