Triple
T8975103
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ana María Mauricia de Austria |
E214366
|
entity |
| Predicate | startTimeNote |
P86020
|
FINISHED |
| Object | marriage to Louis XIII of France |
—
|
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: marriage to Louis XIII of France | Statement: [Ana María Mauricia de Austria, startTimeNote, marriage to Louis XIII of France]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startTimeNote Context triple: [Ana María Mauricia de Austria, startTimeNote, marriage to Louis XIII of France]
-
A.
positionStartTime
Indicates the time at which a position, role, or placement begins.
-
B.
startTimeAsCardinal
Indicates the specific clock time at which an event or action begins, expressed as a cardinal (numeric) value rather than a textual or formatted time.
-
C.
timeStartApprox
Indicates that the associated event or state begins at an approximate, rather than exact, point in time.
-
D.
startDate
Indicates the point in time when an event, state, or relationship begins.
-
E.
startsAt
Indicates that an event, process, or state begins at a specific time, location, or point in a sequence.
- 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_69ca839dbf608190a2f5990477115d29 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6784d1808190899c980f76084ff8 |
completed | April 1, 2026, 12:32 a.m. |
| PD | Predicate disambiguation | batch_69cc5ed9a2d48190ad11381078e823b7 |
completed | March 31, 2026, 11:55 p.m. |
| PDg | Predicate description generation | batch_69cc5fcf24348190b6b845205161c0ee |
completed | March 31, 2026, 11:59 p.m. |
Created at: March 30, 2026, 7:02 p.m.