Triple
T34933216
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Airport Lake fault zone |
E1007497
|
entity |
| Predicate | isPartOfPlateBoundary |
P85491
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Airport Lake fault zone, isPartOfPlateBoundary, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPartOfPlateBoundary Context triple: [Airport Lake fault zone, isPartOfPlateBoundary, true]
-
A.
locatedOnTectonicBoundary
Indicates that one entity is situated directly on or along the tectonic plate boundary associated with another entity.
-
B.
isPartOfTectonicFeature
chosen
Indicates that one geological entity is a component or subdivision of a larger tectonic feature or structure.
-
C.
tectonicPlateBoundaryRelation
Indicates a spatial or geological relationship between tectonic plates at their boundary, such as where they meet, interact, or move relative to each other.
-
D.
plateBoundaryClass
Indicates the type or classification of the boundary between tectonic plates (e.g., convergent, divergent, transform).
-
E.
plateBoundaryBetween
Indicates a geological relationship where a boundary exists between two tectonic plates.
- 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_69f76dc3d83881909d5c3c14455cfa2c |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ff779e3f0c8190a861f1e4000fd9d9 |
completed | May 9, 2026, 6:06 p.m. |
| PD | Predicate disambiguation | batch_69ff77202638819086e4b9f9c0bc7b31 |
completed | May 9, 2026, 6:04 p.m. |
Created at: May 3, 2026, 4 p.m.