Triple
T16442882
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Austrasia |
E399347
|
entity |
| Predicate | importantOffice |
P122807
|
FINISHED |
| Object | Mayor of the Palace |
—
|
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: Mayor of the Palace | Statement: [Austrasia, importantOffice, Mayor of the Palace]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: importantOffice Context triple: [Austrasia, importantOffice, Mayor of the Palace]
-
A.
officialIn
Indicates that an entity holds an official position, role, or office within a specified organization, institution, or jurisdiction.
-
B.
officeEmphasizes
Indicates that an office prioritizes, highlights, or places special importance on a particular issue, value, activity, or characteristic.
-
C.
officeIn
Indicates that one entity has an office located within the premises or jurisdiction of another entity.
-
D.
includedOffice
Indicates that one office is contained within, or forms part of, another office or organizational unit.
-
E.
inOfficeFrom
Indicates that an entity holds a particular office or position starting from a specified date or time.
- 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_69d87f2c6778819080fcfae53be8f12a |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e32cd8d2988190acb5722a15623319 |
completed | April 18, 2026, 7:03 a.m. |
| PD | Predicate disambiguation | batch_69e22701d2288190bf8676050758f172 |
completed | April 17, 2026, 12:26 p.m. |
| PDg | Predicate description generation | batch_69e24556c1348190902a4d116c3137d9 |
completed | April 17, 2026, 2:36 p.m. |
Created at: April 10, 2026, 5:10 a.m.