Triple
T295856
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aleutian Arc |
E6090
|
entity |
| Predicate | isStudiedInField |
P770
|
FINISHED |
| Object | plate tectonics |
—
|
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 tectonics | Statement: [Aleutian Arc, isStudiedInField, plate tectonics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isStudiedInField Context triple: [Aleutian Arc, isStudiedInField, plate tectonics]
-
A.
isStudiedIn
chosen
Indicates that a subject (such as a topic, field, or phenomenon) is examined, researched, or learned about within a particular context, environment, or discipline.
-
B.
offersFieldOfStudy
Indicates that an institution or program provides a particular field of study as an available area of academic focus.
-
C.
hasLanguageOfStudy
Indicates that an entity studies or is engaged in learning a particular language.
-
D.
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.
-
E.
studiedBy
Indicates that a subject (such as a field, topic, or object) is examined, researched, or learned by an agent (such as a person or group).
- 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_69a2e79114b081909490b3bf5a5dbb51 |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2e9e273f88190ac5355d1310376ed |
completed | Feb. 28, 2026, 1:13 p.m. |
| PD | Predicate disambiguation | batch_69a2e9368894819093eeae4347dfcc5a |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:06 p.m.