Triple
T600485
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Argentine Antarctica |
E11480
|
entity |
| Predicate | mainActivities |
P1164
|
FINISHED |
| Object | scientific research |
—
|
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: scientific research | Statement: [Argentine Antarctica, mainActivities, scientific research]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainActivities Context triple: [Argentine Antarctica, mainActivities, scientific research]
-
A.
typicalActivity
chosen
Indicates that an entity is commonly or characteristically engaged in a particular activity.
-
B.
mainIndex
Indicates that one entity serves as the primary or central index or reference point for another entity within a structured system.
-
C.
activityType
Indicates the specific kind or category of action or event that an entity is engaged in or associated with.
-
D.
primaryTask
Indicates that an entity has a main or most important task, role, or function it is responsible for above all others.
-
E.
activityDomain
Indicates the general field, sector, or area of activity within which an entity operates or performs its main actions.
- 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_69a4932779b881908688590d59c71900 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49e574444819087999404f3e3ffd9 |
completed | March 1, 2026, 8:15 p.m. |
| PD | Predicate disambiguation | batch_69a49cf701e08190966d06b9ff4b582b |
completed | March 1, 2026, 8:09 p.m. |
Created at: March 1, 2026, 7:35 p.m.