Triple
T36663566
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aquitanian Stage |
E905197
|
entity |
| Predicate | lowerBoundaryGSSPLocation |
P125709
|
FINISHED |
| Object | Lemme-Carrosio section |
—
|
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: Lemme-Carrosio section | Statement: [Aquitanian Stage, lowerBoundaryGSSPLocation, Lemme-Carrosio section]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lowerBoundaryGSSPLocation Context triple: [Aquitanian Stage, lowerBoundaryGSSPLocation, Lemme-Carrosio section]
-
A.
lowerBoundaryLocation
chosen
Indicates the place or region where the lower or bottom boundary of something is situated.
-
B.
lowerGSSPLocation
Indicates that one location is geographically or spatially situated below another specified location.
-
C.
upperBoundaryGSSPLocation
Indicates the relationship where a location serves as the upper boundary or limit of a GSSP (Global Boundary Stratotype Section and Point) definition.
-
D.
lowerLimit
Indicates that one value serves as the minimum or smallest allowable bound or threshold for another value or range.
-
E.
lowerBoundProperty
Indicates that one entity serves as the minimum or lowest permissible value, limit, or constraint for another entity or quantity.
- 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_69f7c9f5a8848190ba956ff27f44e396 |
completed | May 3, 2026, 10:19 p.m. |
| PD | Predicate disambiguation | batch_69f7c8999a348190abc1895eaa6e036d |
completed | May 3, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:12 p.m.