Triple
T1169713
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Korstian Division |
E24885
|
entity |
| Predicate | hasFieldStationsFor |
P2881
|
FINISHED |
| Object | long-term ecological 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: long-term ecological research | Statement: [Korstian Division, hasFieldStationsFor, long-term ecological research]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFieldStationsFor Context triple: [Korstian Division, hasFieldStationsFor, long-term ecological research]
-
A.
hasComponentStation
Indicates that an entity includes or is associated with a specific station as one of its component parts.
-
B.
hasGhostStations
Indicates that a transportation system or network includes disused, closed, or never-opened stations that still physically exist.
-
C.
hasStationBuilding
Indicates that a station is associated with or includes a station building as part of its facilities.
-
D.
containsResearchStation
chosen
Indicates that one entity geographically includes or hosts a research station within its boundaries.
-
E.
hasFieldDivision
Indicates that one entity is organizationally divided into, or associated with, a specific field-based subdivision 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_69a494082a7c819095004f423f294a64 |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4bce821b481908bc278a3fa7973f4 |
completed | March 1, 2026, 10:25 p.m. |
| PD | Predicate disambiguation | batch_69a4bb5656948190b0b1d5446ad06005 |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:45 p.m.