Triple
T19708922
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spanish conquest of Iberian Navarre |
E473289
|
entity |
| Predicate | mainDateRange |
P46071
|
FINISHED |
| Object | early 16th 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: early 16th century | Statement: [Spanish conquest of Iberian Navarre, mainDateRange, early 16th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainDateRange Context triple: [Spanish conquest of Iberian Navarre, mainDateRange, early 16th century]
-
A.
representsDateRange
chosen
Indicates that a subject is associated with, valid for, or applicable during a specific start-to-end date range.
-
B.
collectionTimespan
Indicates the time period over which a collection exists, is accumulated, or is considered valid.
-
C.
createdBetween
Indicates that something was created within a specified start and end time or date range.
-
D.
typicalEndDateRange
Indicates the usual or expected range of end dates associated with an event, activity, or time-bounded entity.
-
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_69d8e516dd048190a0b6c93ea3e71f58 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e64406f9808190acd74aa03c392eb0 |
completed | April 20, 2026, 3:19 p.m. |
| PD | Predicate disambiguation | batch_69e530438c60819082364c7be3eef6f0 |
completed | April 19, 2026, 7:42 p.m. |
Created at: April 10, 2026, 1:46 p.m.