Triple
T35097694
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kotelnich |
E1012909
|
entity |
| Predicate | hasNearbyScientificActivity |
P181755
|
FINISHED |
| Object | paleontological excavations |
—
|
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: paleontological excavations | Statement: [Kotelnich, hasNearbyScientificActivity, paleontological excavations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbyScientificActivity Context triple: [Kotelnich, hasNearbyScientificActivity, paleontological excavations]
-
A.
hasResearchActivities
Indicates that an entity engages in, conducts, or is associated with research-related activities.
-
B.
hasScientificImportanceNearby
chosen
Indicates that something in the surrounding area possesses notable scientific significance or value.
-
C.
hasResearchActivityLevel
Indicates the degree or intensity of research-related activity associated with an entity.
-
D.
hasScientificInterestIn
Indicates that one entity holds a scientific curiosity, concern, or research focus directed toward another entity.
-
E.
nearbyScientificAchievement
Indicates that a scientific achievement occurs or exists in close spatial proximity to a specified reference point or 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_69f76dd556248190808b4c4f43debebb |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fffc783b648190bcd7df017514d206 |
completed | May 10, 2026, 3:33 a.m. |
| PD | Predicate disambiguation | batch_69fffc03fa24819099e12413dc6e0afd |
completed | May 10, 2026, 3:31 a.m. |
Created at: May 3, 2026, 4:01 p.m.