Triple
T15821870
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Earl of Buckingham |
E383632
|
entity |
| Predicate | heldInPeriod |
P97182
|
FINISHED |
| Object | late 14th 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: late 14th century | Statement: [Earl of Buckingham, heldInPeriod, late 14th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heldInPeriod Context triple: [Earl of Buckingham, heldInPeriod, late 14th century]
-
A.
appearsInTimePeriod
chosen
Indicates that an entity is present, active, or occurs within a specified time period.
-
B.
meetsInTimePeriod
Indicates that two entities encounter or come together during a specified time period.
-
C.
isSetInTimePeriod
Indicates that an event, story, or situation takes place within a specified time period.
-
D.
compiledInPeriod
Indicates that the creation or compilation of something occurred within a specified time period.
-
E.
occurredBetween
Indicates that an event or action took place within the time interval defined by two temporal boundaries.
- 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_69d86da2858c819090cc8481e7207b6e |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e0c4a887d881908f74a1fcba390727 |
completed | April 16, 2026, 11:14 a.m. |
| PD | Predicate disambiguation | batch_69e005418f588190824d91ff7974dada |
completed | April 15, 2026, 9:38 p.m. |
Created at: April 10, 2026, 4:49 a.m.