Triple
T27146601
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Van Heemstra family |
E681964
|
entity |
| Predicate | knownSinceCentury |
P112323
|
FINISHED |
| Object | 15th century |
—
|
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: 15th century | Statement: [Van Heemstra family, knownSinceCentury, 15th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: knownSinceCentury Context triple: [Van Heemstra family, knownSinceCentury, 15th century]
-
A.
coveredSinceCentury
Indicates that one entity has been covered, coated, or kept under coverage continuously starting from a specified century.
-
B.
existsSinceCentury
Indicates that an entity has existed or been in effect since a specified century.
-
C.
observedSinceCentury
chosen
Indicates that one entity has been observed or documented as existing or occurring since a specified century.
-
D.
usedSinceCentury
Indicates that something has been in use starting from a specified century.
-
E.
displayedSinceCentury
Indicates that something has been on display continuously or from a specified century onward.
- 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_69eefacca3888190b67238d380e8f28b |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f6640168948190811bd5f933a87cf5 |
completed | May 2, 2026, 8:52 p.m. |
| PD | Predicate disambiguation | batch_69f6633451948190bcc0410602bb4914 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 27, 2026, 9:11 a.m.