Triple
T14687502
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rivera Triple Junction region |
E344946
|
entity |
| Predicate | isResearchFocusFor |
P70296
|
FINISHED |
| Object | plate boundary dynamics |
—
|
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: plate boundary dynamics | Statement: [Rivera Triple Junction region, isResearchFocusFor, plate boundary dynamics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isResearchFocusFor Context triple: [Rivera Triple Junction region, isResearchFocusFor, plate boundary dynamics]
-
A.
hasResearchArea
Indicates that an entity (such as a person, project, or organization) is associated with or focused on a particular field or area of research.
-
B.
usesResearchSubject
Indicates that one entity employs or utilizes another entity as a research subject in a study or investigation.
-
C.
isResearchOriented
Indicates that an entity is primarily focused on conducting, supporting, or advancing research activities.
-
D.
researchTopic
Indicates that a subject conducts or focuses research on a particular topic or area of study.
-
E.
isSubjectOfStudy
chosen
Indicates that an entity is the focus or topic being examined, researched, or analyzed in a study or investigation.
- 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_69d822e34b348190ada4d1cdb6c7c226 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb58306548190b981956a83a84b95 |
completed | April 14, 2026, 9:45 p.m. |
| PD | Predicate disambiguation | batch_69de6579fb7881909becc8f5822b39d4 |
completed | April 14, 2026, 4:04 p.m. |
Created at: April 10, 2026, 1:28 a.m.