Triple
T21751736
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Neolithic Europe |
E536930
|
entity |
| Predicate | hasLaterStartInRegion |
P145230
|
FINISHED |
| Object | northern Europe |
—
|
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: northern Europe | Statement: [Neolithic Europe, hasLaterStartInRegion, northern Europe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLaterStartInRegion Context triple: [Neolithic Europe, hasLaterStartInRegion, northern Europe]
-
A.
startsInRegion
Indicates that an entity’s starting point or initial location lies within a specified region.
-
B.
endsInRegion
Indicates that an entity’s spatial or temporal extent terminates within the boundaries of a specified region.
-
C.
startedForRegion
Indicates that an activity, process, or service has been initiated specifically for a given geographic or administrative region.
-
D.
hasSuccessorLanguageInRegion
Indicates that one language is followed or replaced by another language within a specific geographic region.
-
E.
hasPosteriorRegion
Indicates that one entity constitutes or occupies the rear or back (posterior) region of another entity.
- 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_69e0c46eab808190b848242d63a17c47 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f01d8a6d4881908cc69e7247cce3a5 |
completed | April 28, 2026, 2:38 a.m. |
| PD | Predicate disambiguation | batch_69e6969c16fc8190b5126c169317d85d |
completed | April 20, 2026, 9:11 p.m. |
| PDg | Predicate description generation | batch_69e69f3ed4408190a4a78410bf660c44 |
completed | April 20, 2026, 9:48 p.m. |
Created at: April 16, 2026, 6:50 p.m.