Triple
T7376630
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pine Island Glacier |
E170140
|
entity |
| Predicate | majorContributorTo |
P477
|
FINISHED |
| Object | global sea-level rise |
—
|
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: global sea-level rise | Statement: [Pine Island Glacier, majorContributorTo, global sea-level rise]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorContributorTo Context triple: [Pine Island Glacier, majorContributorTo, global sea-level rise]
-
A.
hasContributionFrom
Indicates that something (such as a work, project, or outcome) is created, influenced, or supported in part by a specified contributor.
-
B.
notableContribution
chosen
Indicates that an entity has made a significant, recognized contribution to another entity, field, work, or endeavor.
-
C.
notableContributionField
Indicates the field or domain in which an entity has made a significant or noteworthy contribution.
-
D.
firstContributor
Indicates that the subject is the earliest or initial contributor to the object within a given context or project.
-
E.
hadInfluenceOn
Indicates that one entity affected, shaped, or contributed to the development, behavior, or characteristics of another entity.
- 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_69c68a5bfaac81909ce7f001dfb70c76 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f1a8b18c8190ad1a19521eda2319 |
completed | March 27, 2026, 9:07 p.m. |
| PD | Predicate disambiguation | batch_69c6f02ee3e08190a7a00c981129b22c |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:07 p.m.