Triple
T10475928
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Camino de Santiago |
E247043
|
entity |
| Predicate | hasRevivalPeriod |
P48377
|
FINISHED |
| Object | late 20th 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 20th century | Statement: [Camino de Santiago, hasRevivalPeriod, late 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRevivalPeriod Context triple: [Camino de Santiago, hasRevivalPeriod, late 20th century]
-
A.
hasRevivalsIn
Indicates that something has been brought back, renewed, or reintroduced in specific times, places, or contexts.
-
B.
periodOfRevival
chosen
Indicates a time span during which something that had declined or been inactive experiences renewed growth, activity, or prominence.
-
C.
hasRevelationPeriod
Indicates the time span or phase during which a revelation, disclosure, or unveiling of something occurs or is valid.
-
D.
hasReviewPeriod
Indicates that an entity is associated with a specific time span during which it is subject to review or evaluation.
-
E.
revivedAtLevel
Indicates that an entity was brought back to life or reactivated when a specified level or stage was reached.
- 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_69d381c16c248190a2fe5b471e584e9c |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d5094f6b408190a5a26b1a82e4a02b |
completed | April 7, 2026, 1:40 p.m. |
| PD | Predicate disambiguation | batch_69d4fb84bafc8190819757b93620508a |
completed | April 7, 2026, 12:41 p.m. |
Created at: April 6, 2026, 12:21 p.m.