Triple
T36663651
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Langhian |
E905199
|
entity |
| Predicate | stratotypeLocation |
P29619
|
FINISHED |
| Object | northern 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: northern Italy | Statement: [Langhian, stratotypeLocation, northern Italy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stratotypeLocation Context triple: [Langhian, stratotypeLocation, northern Italy]
-
A.
stratotypeRegion
chosen
Indicates the region or geographic area that serves as the reference or standard location (stratotype) for a particular stratigraphic unit or interval.
-
B.
stratotypeSection
Indicates the reference rock section formally designated as the standard or type example for a particular stratigraphic unit or boundary.
-
C.
locationOfStructure
Indicates that a particular structure is situated at or occupies a specific location.
-
D.
strategicLocation
Indicates that an entity is positioned in a place of particular tactical or strategic importance relative to goals, resources, or other entities.
-
E.
subjectLocationType
Indicates the type or category of location associated with the subject in the relationship.
- 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.