Triple
T963975
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | William d’Aubigny, 1st Earl of Arundel |
E20794
|
entity |
| Predicate | titleCreationDate |
P6878
|
FINISHED |
| Object | c. 1138 |
—
|
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: c. 1138 | Statement: [William d’Aubigny, 1st Earl of Arundel, titleCreationDate, c. 1138]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleCreationDate Context triple: [William d’Aubigny, 1st Earl of Arundel, titleCreationDate, c. 1138]
-
A.
createdAt
Indicates the date and time at which an entity was initially created or came into existence.
-
B.
createdAtRidge
Indicates that something was created or originated at a specific ridge location.
-
C.
dateOf
chosen
Indicates that one entity specifies the calendar date associated with another entity, such as when it occurred, was created, or is scheduled.
-
D.
createdAs
Indicates that one entity was originally made, designed, or brought into existence in the form, role, or identity specified by another entity.
-
E.
createdTo
Indicates that one entity was brought into existence, produced, or designed specifically for the purpose, use, or function of another entity.
- 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_69a493b21f2881908132dcf45dcd2f36 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b4303e5881909d101d11f9732c75 |
completed | March 1, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69a4b2a2e23c8190b932fe88b02f995d |
completed | March 1, 2026, 9:41 p.m. |
Created at: March 1, 2026, 7:40 p.m.