Triple
T4172156
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ladoga ringed seal |
E86387
|
entity |
| Predicate | isolation |
P41105
|
FINISHED |
| Object | geographically isolated |
—
|
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: geographically isolated | Statement: [Ladoga ringed seal, isolation, geographically isolated]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isolation Context triple: [Ladoga ringed seal, isolation, geographically isolated]
-
A.
isolatedBy
Indicates that one entity has been separated or kept apart from another entity or set of entities, preventing interaction or influence between them.
-
B.
hasIsolation
Indicates that an entity is separated or kept apart from others, typically to prevent interaction, influence, or contamination.
-
C.
linguisticIsolation
Indicates a condition where an entity is separated from others in terms of language, lacking shared or effective linguistic communication.
-
D.
is
Indicates that two entities are equivalent, share an attribute, or stand in a specified state or relation to each other.
-
E.
isIsolated
chosen
Indicates that an entity exists or occurs separately from others, without direct contact, interaction, or connection.
- 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_69aed93de98c8190ad838ce507b77c8a |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af02c9e12c81908d0b22671fea2453 |
completed | March 9, 2026, 5:26 p.m. |
| PD | Predicate disambiguation | batch_69af018fb0948190a9701b2e8e5d9bac |
completed | March 9, 2026, 5:21 p.m. |
Created at: March 9, 2026, 3:45 p.m.