Triple
T37404146
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kerevat |
E929076
|
entity |
| Predicate | hasAgriculturalResearchStation |
P2881
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Kerevat, hasAgriculturalResearchStation, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAgriculturalResearchStation Context triple: [Kerevat, hasAgriculturalResearchStation, true]
-
A.
containsResearchStation
chosen
Indicates that one entity geographically includes or hosts a research station within its boundaries.
-
B.
hasResearchCentersIn
Indicates that an entity maintains or operates research centers located within a specified place or region.
-
C.
establishedResearchStation
Indicates that an entity founded or set up a research station at a particular location or for a particular purpose.
-
D.
isResearchInstitution
Indicates that an entity functions primarily as an organization dedicated to conducting scientific or scholarly research.
-
E.
hasResearchInfrastructure
Indicates that an entity possesses, controls, or provides access to facilities, equipment, or resources used to conduct research.
- 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_69f76ebbf79c8190b85bbcf3a6be57e4 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fba68077788190b311e027435fcf87 |
completed | May 6, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69fba34c65ac8190b298f0f00d1dcc0e |
completed | May 6, 2026, 8:23 p.m. |
Created at: May 3, 2026, 4:16 p.m.