Triple
T1960665
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tharp-Heezen Seamounts |
E42376
|
entity |
| Predicate | namedForRoleIn |
P4342
|
FINISHED |
| Object | development of plate tectonic theory |
—
|
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: development of plate tectonic theory | Statement: [Tharp-Heezen Seamounts, namedForRoleIn, development of plate tectonic theory]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: namedForRoleIn Context triple: [Tharp-Heezen Seamounts, namedForRoleIn, development of plate tectonic theory]
-
A.
namedForRank
Indicates that something is named after a specific rank or title held by an entity.
-
B.
namedPersonRole
Indicates that a person is identified by name as holding a specific role or position in a given context.
-
C.
namedTo
Indicates that one entity has been given or assigned a specific name referring to another entity.
-
D.
refersToRole
chosen
Indicates that one entity designates, mentions, or points to another entity specifically in its capacity as a role or position.
-
E.
namedForPoliticalRole
Indicates that one entity is named after another entity specifically because of that entity’s political office, position, or role.
- 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_69a8870eea088190a38781990812a9bc |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abb68a8e608190bc37a85913b3cd44 |
completed | March 7, 2026, 5:24 a.m. |
| PD | Predicate disambiguation | batch_69abaff5dbd48190a9d36ca60de151db |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:36 p.m.