Triple
T28667367
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Delapore |
E725617
|
entity |
| Predicate | familyHistorySpans |
P99368
|
FINISHED |
| Object | centuries |
—
|
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: centuries | Statement: [Delapore, familyHistorySpans, centuries]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: familyHistorySpans Context triple: [Delapore, familyHistorySpans, centuries]
-
A.
chronologyWithinFamily
chosen
Indicates that one family-related event or state occurs within the temporal span defined by another family-related event or state.
-
B.
historicalFamily
Indicates a familial relationship that existed between entities in the past, regardless of whether it still holds in the present.
-
C.
genealogicalLine
Indicates a genealogical relationship connecting individuals through lines of descent or ancestry.
-
D.
heldByFamilySince
Indicates that something has been continuously possessed or owned by the same family from a certain point in time.
-
E.
sharesFamilyLineageWith
Indicates that two entities descend from the same family line or share common ancestors.
- 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_69f01d85be388190b669a0e401e2f2c4 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f6aaf50be08190a2b62a6d881f8aee |
completed | May 3, 2026, 1:55 a.m. |
| PD | Predicate disambiguation | batch_69f6aa1c555081908787dbf76147f180 |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 28, 2026, 5:01 a.m.