Triple
T8718785
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Archbishop of Paris |
E206959
|
entity |
| Predicate | currentHolderInstalled |
P7037
|
FINISHED |
| Object | 2022-05-23 |
—
|
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: 2022-05-23 | Statement: [Archbishop of Paris, currentHolderInstalled, 2022-05-23]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: currentHolderInstalled Context triple: [Archbishop of Paris, currentHolderInstalled, 2022-05-23]
-
A.
hasCurrentHolder
Indicates that a specified entity is the present holder, possessor, or occupant of another entity (such as a position, title, asset, or object).
-
B.
currentlyHeldBy
Indicates that an entity is at present in the possession, control, or custody of another entity.
-
C.
isUsuallyHeldBy
Indicates that something is most commonly or typically possessed, carried, or controlled by a particular entity.
-
D.
currentHolderStart
chosen
Indicates the point in time when an entity’s current holder or possessor first began holding it.
-
E.
hasHolding
Indicates that one entity possesses, controls, or maintains ownership or custody of another entity as an asset or item.
- 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_69ca83572d4881909bef3be2b578d539 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5d014e208190a4c6055901580d0c |
completed | March 31, 2026, 11:47 p.m. |
| PD | Predicate disambiguation | batch_69cc456e806c819087e7d66ee737f242 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:36 p.m.