Triple
T30744227
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Agate Basin complex |
E782773
|
entity |
| Predicate | hasHaftElement |
P173424
|
FINISHED |
| Object | ground basal edges |
—
|
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: ground basal edges | Statement: [Agate Basin complex, hasHaftElement, ground basal edges]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHaftElement Context triple: [Agate Basin complex, hasHaftElement, ground basal edges]
-
A.
hasFrameElement
Indicates that a frame (or structured conceptual scenario) includes or is associated with a specific frame element (a participant, role, or component within that frame).
-
B.
hasPar
Indicates a relationship where one entity has another entity as its parent.
-
C.
hasXAelements
Indicates that one entity possesses or contains a certain number (X) of elements of a specified type (A).
-
D.
hasBruteElement
Indicates that an entity possesses or is associated with a raw, force-based, or brute-type elemental property.
-
E.
hasMainElements
Indicates that something possesses or is composed of its primary or most important constituent parts.
- 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_69f224aeb1588190897d395e8ed2acb8 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6b56ed31481908c3e5d749e46bad9 |
completed | May 3, 2026, 2:39 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a7bdb481908d16a32f49e38c2c |
completed | May 3, 2026, 2:32 a.m. |
| PDg | Predicate description generation | batch_69f6b49339048190b617a6749f648825 |
completed | May 3, 2026, 2:36 a.m. |
Created at: April 29, 2026, 8:38 p.m.