Triple
T33021503
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pannonian Sea |
E844923
|
entity |
| Predicate | leftGeologicalRemnant |
P175924
|
FINISHED |
| Object | Pannonian Basin |
—
|
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: Pannonian Basin | Statement: [Pannonian Sea, leftGeologicalRemnant, Pannonian Basin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: leftGeologicalRemnant Context triple: [Pannonian Sea, leftGeologicalRemnant, Pannonian Basin]
-
A.
geologicalFormation
Indicates that one entity is a geological structure or feature that characterizes or composes the physical makeup of another entity.
-
B.
hasGeologicalSignificance
Indicates that something possesses notable importance or relevance within a geological context, such as Earth’s structure, history, or processes.
-
C.
locatedInGeologicPast
Indicates that something existed or occurred in a specific place during a past geologic time period.
-
D.
hasGeologicalEvidenceOf
Indicates that there is geological data or features supporting the existence, occurrence, or impact of a specified phenomenon or event.
-
E.
geologicalCoreOf
Indicates that one entity is the central, innermost geological part or core of another geological structure or body.
- 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_69f34950749c8190ae05cd27adb16d58 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d74b20a48190900dda1014cc13a8 |
completed | May 3, 2026, 5:04 a.m. |
| PD | Predicate disambiguation | batch_69f6d26f27dc8190ae426a3e1573933e |
completed | May 3, 2026, 4:43 a.m. |
| PDg | Predicate description generation | batch_69f6d749e7f081909c8196898c4191ad |
completed | May 3, 2026, 5:04 a.m. |
Created at: May 1, 2026, 1:23 a.m.