Triple
T1755778
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Queen Charlotte Fault |
E38542
|
entity |
| Predicate | ageContext |
P32800
|
FINISHED |
| Object | Cenozoic plate boundary feature |
—
|
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: Cenozoic plate boundary feature | Statement: [Queen Charlotte Fault, ageContext, Cenozoic plate boundary feature]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ageContext Context triple: [Queen Charlotte Fault, ageContext, Cenozoic plate boundary feature]
-
A.
agePattern
Indicates a relationship where entities share or follow a specific configuration, distribution, or rule regarding their ages.
-
B.
ageProgression
Indicates a temporal relationship where an entity’s age increases or advances over time.
-
C.
addressContext
Indicates the situational or conversational setting in which an address (such as a location, contact, or reference) is used or interpreted.
-
D.
ageGroup
Indicates the categorical age range or bracket to which an entity belongs.
-
E.
contextOf
Indicates that one entity provides the situational, informational, or environmental background within which another entity exists, occurs, or is interpreted.
- 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_69a8862bdb2081908aefe831c8aa8017 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69aba6a63f588190b53b39c6b97d74f4 |
completed | March 7, 2026, 4:16 a.m. |
| PD | Predicate disambiguation | batch_69aa61c7ef4c8190abec87c96a787d82 |
completed | March 6, 2026, 5:10 a.m. |
| PDg | Predicate description generation | batch_69aba6a4c84c8190b3ce0bf69c2b5f6d |
completed | March 7, 2026, 4:16 a.m. |
Created at: March 4, 2026, 7:31 p.m.