Triple
T36663567
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aquitanian Stage |
E905197
|
entity |
| Predicate | lowerBoundaryGSSPCountry |
P125709
|
FINISHED |
| Object | Italy |
—
|
NE NERFINISHED |
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: Italy | Statement: [Aquitanian Stage, lowerBoundaryGSSPCountry, Italy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lowerBoundaryGSSPCountry Context triple: [Aquitanian Stage, lowerBoundaryGSSPCountry, Italy]
-
A.
lowerGSSPCountry
Indicates that one country has a lower Global Social and Sustainability Performance (GSSP) score than another country.
-
B.
upperBoundaryGSSPCountry
Indicates that one entity defines or represents the upper geographic boundary of a GSSP-designated country in a stratigraphic or spatial context.
-
C.
lowerBoundaryLocation
chosen
Indicates the place or region where the lower or bottom boundary of something is situated.
-
D.
lowestAdministrativeLevel
Indicates that the subject entity is at the smallest or most granular administrative division within a given territorial or organizational hierarchy.
-
E.
lowerGSSPLocation
Indicates that one location is geographically or spatially situated below another specified location.
- 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_69f76e6e3b908190970251b30f76ad71 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f9fd6834cc8190aa27153d6a99f3bb |
completed | May 5, 2026, 2:23 p.m. |
| PD | Predicate disambiguation | batch_69f7cf7890008190a8bc355ff2d61c86 |
completed | May 3, 2026, 10:43 p.m. |
Created at: May 3, 2026, 4:12 p.m.