Triple
T3012472
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ross Dependency |
E82252
|
entity |
| Predicate | primaryHumanPresence |
P21135
|
FINISHED |
| Object | scientific and support personnel |
—
|
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 and support personnel | Statement: [Ross Dependency, primaryHumanPresence, scientific and support personnel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryHumanPresence Context triple: [Ross Dependency, primaryHumanPresence, scientific and support personnel]
-
A.
hasHumanPresence
Indicates that humans are physically present in or occupying a given location, object, or context.
-
B.
primaryVisitors
Indicates that certain entities are the main or most important visitors associated with another entity or context.
-
C.
hasPrimaryOccupants
chosen
Indicates that certain entities are the main or principal occupants of another entity (such as a space, structure, or location).
-
D.
hasNonHumanResident
Indicates that a place or location is inhabited or occupied by one or more non-human entities.
-
E.
modernPresence
Indicates that something exists, appears, or is active in the contemporary or present-day context.
- 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_69ad8b1eb53481908c39bbcd1ec104b2 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad9a66c334819082d1d320c48eca1b |
completed | March 8, 2026, 3:48 p.m. |
| PD | Predicate disambiguation | batch_69ad961a97188190809dc73430a8eda8 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 3 p.m.