Triple
T10177713
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Takuu |
E235895
|
entity |
| Predicate | geographicalIsolation |
P28635
|
FINISHED |
| Object | high |
—
|
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: high | Statement: [Takuu, geographicalIsolation, high]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: geographicalIsolation Context triple: [Takuu, geographicalIsolation, high]
-
A.
geographicIsolation
chosen
Indicates that an entity is separated from others by physical distance or natural barriers, limiting interaction or exchange between them.
-
B.
topographicIsolation
Indicates the distance from a geographic feature to the nearest point of equal or greater elevation, expressing how isolated it is from higher terrain.
-
C.
isolatedBy
Indicates that one entity has been separated or kept apart from another entity or set of entities, preventing interaction or influence between them.
-
D.
geographicDistribution
Indicates the spatial range or area over which something occurs, exists, or is found.
-
E.
biogeographicEvent
Indicates an event that changes or characterizes the geographic distribution of organisms or biological communities over space and time.
- 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_69ca84d1d5f88190ab878a1021ecff68 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdecd4e3188190aa5d9ee95595f4a7 |
completed | April 2, 2026, 4:13 a.m. |
| PD | Predicate disambiguation | batch_69cd7c79f21c8190a7f31b2eab80b8ba |
completed | April 1, 2026, 8:13 p.m. |
Created at: March 30, 2026, 9:11 p.m.