Triple
T29801355
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hugo de Lacy |
E756709
|
entity |
| Predicate | workSetInPeriod |
P71319
|
FINISHED |
| Object | medieval period |
—
|
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: medieval period | Statement: [Hugo de Lacy, workSetInPeriod, medieval period]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workSetInPeriod Context triple: [Hugo de Lacy, workSetInPeriod, medieval period]
-
A.
workSetDuring
chosen
Indicates that an action or relationship occurs within a specified time period or temporal setting.
-
B.
workPeriod
Indicates the span of time during which an entity is engaged in a particular work or employment activity.
-
C.
timePeriodOfWorks
Indicates the span of time during which the associated works were created, produced, or active.
-
D.
partOfWorkPeriod
Indicates that a specific time span is contained within, and belongs to, a larger defined work period.
-
E.
containsWorkFromPeriod
Indicates that something includes or features work that originates from a specified historical or temporal period.
- 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_69f22454583081908927516cb9938d1d |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f707f7959881908f037f0d6b1d0c36 |
completed | May 3, 2026, 8:31 a.m. |
| PD | Predicate disambiguation | batch_69f700fc274c8190a128593dc7c7abd0 |
completed | May 3, 2026, 8:02 a.m. |
Created at: April 29, 2026, 5:18 p.m.