Triple
T3408715
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vernadsky Research Base |
E71837
|
entity |
| Predicate | permanentStaffPresence |
P29647
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Vernadsky Research Base, permanentStaffPresence, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: permanentStaffPresence Context triple: [Vernadsky Research Base, permanentStaffPresence, yes]
-
A.
fieldOfficePresence
Indicates that an entity maintains a physical field office or on-the-ground operational presence in a particular location or jurisdiction.
-
B.
hasHumanPresence
Indicates that humans are physically present in or occupying a given location, object, or context.
-
C.
modernPresence
Indicates that something exists, appears, or is active in the contemporary or present-day context.
-
D.
isPermanentlyCrewed
chosen
Indicates that an object, such as a facility or vehicle, consistently has a crew present on a continuous, ongoing basis without planned periods of being uncrewed.
-
E.
inOfficeDuring
Indicates that an entity holds or occupies an office or position throughout a specified time period.
- 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_69ad85ac312481909e7027ced1456a9f |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb9056acc8190a9c50ec374851ac8 |
completed | March 8, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69adadfa73ac8190a163f93e88d217f8 |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:15 p.m.