Triple
T27239388
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chugach terrane |
E687160
|
entity |
| Predicate | containsStructures |
P135717
|
FINISHED |
| Object | thrust faults |
—
|
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: thrust faults | Statement: [Chugach terrane, containsStructures, thrust faults]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsStructures Context triple: [Chugach terrane, containsStructures, thrust faults]
-
A.
haveStructure
Indicates that an entity possesses a particular internal organization, arrangement, or structural composition.
-
B.
containsStructureFrom
Indicates that one entity includes or incorporates a structural component originating from another entity.
-
C.
hasHumanStructure
Indicates that one entity possesses or exhibits a structural form or organization characteristic of humans.
-
D.
hasStructureCount
Indicates the number of structures associated with or contained by a given entity.
-
E.
containsStructuralUnit
chosen
Indicates that one entity includes or encompasses another entity as a structural subunit or component within its overall structure.
- 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_69ef355547408190b5ca0d777c65040a |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69fd0d0ba5c48190bddb3f0e6637544c |
completed | May 7, 2026, 10:07 p.m. |
| PD | Predicate disambiguation | batch_69fd0c4324a8819086c90adf46216e0e |
completed | May 7, 2026, 10:03 p.m. |
Created at: April 27, 2026, 10:36 a.m.