Triple
T10163624
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tocco |
E233951
|
entity |
| Predicate | historicallyActiveInPeriod |
P7685
|
FINISHED |
| Object | Late Middle Ages |
—
|
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 Middle Ages | Statement: [Tocco, historicallyActiveInPeriod, Late Middle Ages]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicallyActiveInPeriod Context triple: [Tocco, historicallyActiveInPeriod, Late Middle Ages]
-
A.
historicallyActiveIn
chosen
Indicates that an entity was active or engaged in significant activities within a particular place or context during a past historical period.
-
B.
activeInYears
Indicates that an entity was active or operational during the specified years or year range.
-
C.
hadPeakInfluencePeriod
Indicates the time span during which an entity exerted its greatest or most significant influence.
-
D.
activeInYear
Indicates that an entity was active, functioning, or operational during a specified year.
-
E.
hasHistoryPeriod
Indicates that something is associated with, belongs to, or occurs within a specific historical period or era.
- 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_69ca848e80748190b91d1e04d35512c7 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cdec6a7bb48190952f4318af9cc32b |
completed | April 2, 2026, 4:11 a.m. |
| PD | Predicate disambiguation | batch_69cd4ba795808190acc9124c98c6e40f |
completed | April 1, 2026, 4:45 p.m. |
Created at: March 30, 2026, 9:09 p.m.