Triple
T331374
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marie Tharp |
E6631
|
entity |
| Predicate | interpretedAsEvidenceFor |
P3650
|
FINISHED |
| Object | seafloor spreading |
—
|
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: seafloor spreading | Statement: [Marie Tharp, interpretedAsEvidenceFor, seafloor spreading]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: interpretedAsEvidenceFor Context triple: [Marie Tharp, interpretedAsEvidenceFor, seafloor spreading]
-
A.
providesEvidenceFor
chosen
Indicates that one entity serves as support, justification, or proof for the validity or truth of another entity.
-
B.
interpretedAs
Indicates that something is understood, perceived, or taken to mean something else, often based on context or subjective judgment.
-
C.
usedEvidenceType
Indicates that a particular type or category of evidence was employed or relied upon in a given context or activity.
-
D.
interpretedInCase
Indicates that something is understood, analyzed, or given meaning within the context of a particular case or specific situational scenario.
-
E.
believedBy
Indicates that a particular proposition, statement, or entity is held to be true or accepted as real by a specified believer.
- 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_69a2e79434908190a9d5afe415153ad9 |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2eaafd1a48190a6d001af3c2a5318 |
completed | Feb. 28, 2026, 1:16 p.m. |
| PD | Predicate disambiguation | batch_69a2e94c6d8881908239d3788c018adf |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.