Triple
T36663573
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aquitanian Stage |
E905197
|
entity |
| Predicate | upperBoundaryGSSPLocation |
P186133
|
FINISHED |
| Object | La Vedova Beach 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: La Vedova Beach section | Statement: [Aquitanian Stage, upperBoundaryGSSPLocation, La Vedova Beach section]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: upperBoundaryGSSPLocation Context triple: [Aquitanian Stage, upperBoundaryGSSPLocation, La Vedova Beach section]
-
A.
upperBoundaryType
Indicates the kind or classification of the upper boundary that limits or caps a given range, interval, or extent.
-
B.
upperLimit
Indicates that one entity specifies the maximum allowable value, quantity, or boundary for another entity or condition.
-
C.
topBoundary
Indicates that one entity serves as the uppermost limit, edge, or border of another entity or region.
-
D.
upperBranchLocation
Indicates that one entity is located in the upper branch or higher-level subdivision of another entity’s structure or hierarchy.
-
E.
upperSlopeAngle
Indicates the angle of the slope on the upper portion of an object or surface relative to a reference plane or direction.
- 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_69f76e6e3b908190970251b30f76ad71 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f7c83f5960819089610ed39c839678 |
completed | May 3, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69f7c4796ebc819084a0dc08505e5f14 |
completed | May 3, 2026, 9:56 p.m. |
| PDg | Predicate description generation | batch_69f7c776b4088190bef550c869da530d |
completed | May 3, 2026, 10:08 p.m. |
Created at: May 3, 2026, 4:12 p.m.