Triple
T12628682
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anatolian Plate |
E301582
|
entity |
| Predicate | boundaryTypeNorth |
P105984
|
FINISHED |
| Object | transform boundary |
—
|
LITERAL FINISHED |
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: transform boundary | Statement: [Anatolian Plate, boundaryTypeNorth, transform boundary]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: boundaryTypeNorth Context triple: [Anatolian Plate, boundaryTypeNorth, transform boundary]
-
A.
northernBoundaryReference
Indicates the feature or element that serves as the reference for defining the northern boundary of something.
-
B.
northernBoundaryExtendedTo
Indicates that the northern boundary of one entity has been lengthened or expanded to reach or include another specified reference point or area.
-
C.
borderedToNorthBy
Indicates that one entity lies directly to the north of another, sharing a common boundary along its southern edge.
-
D.
northTerminusType
Indicates the type or nature of the northern endpoint or terminus of a route, line, or similar linear feature.
-
E.
boundaryName
Indicates the designated name or label assigned to a specific boundary or border between entities.
- 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_69d7bdeaf49c8190b13800111fa77ea3 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d9617b07ec8190b714f04ae6654060 |
completed | April 10, 2026, 8:45 p.m. |
| PD | Predicate disambiguation | batch_69d960b195108190ac25bd95e644ace4 |
completed | April 10, 2026, 8:42 p.m. |
| PDg | Predicate description generation | batch_69d96179c7648190a05a13991d62bebb |
completed | April 10, 2026, 8:45 p.m. |
Created at: April 9, 2026, 5:15 p.m.