Triple
T10411550
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Caen stone |
E245402
|
entity |
| Predicate | peakExportPeriod |
P93994
|
FINISHED |
| Object | 11th–13th 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: 11th–13th centuries | Statement: [Caen stone, peakExportPeriod, 11th–13th centuries]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: peakExportPeriod Context triple: [Caen stone, peakExportPeriod, 11th–13th centuries]
-
A.
peakServicePeriod
Indicates the time interval during which a service experiences its highest or most intensive level of use or operation.
-
B.
peakDays
Indicates the days on which something reaches its highest or most intense level of activity, usage, or occurrence.
-
C.
peakDay
Indicates the specific day on which a quantity, activity, or effect reaches its maximum level within a given period.
-
D.
pegPeriodEnd
Indicates the date or point in time at which a pegged or fixed rate, value, or condition ceases to apply.
-
E.
peakStatus
Indicates the condition or phase of something at its highest or most intense point in its progression or lifecycle.
- F. None of above. chosen
Provenance (4 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_69d381be340c8190b05998703d42d224 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4e9fc72d081908d81c71133973daf |
completed | April 7, 2026, 11:26 a.m. |
| PD | Predicate disambiguation | batch_69d4dfb6f160819090040644a12395ec |
completed | April 7, 2026, 10:43 a.m. |
| PDg | Predicate description generation | batch_69d4e91ce2008190af252c140370b7f2 |
completed | April 7, 2026, 11:23 a.m. |
Created at: April 6, 2026, 12:10 p.m.