Triple
T3357211
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | leopard seal |
E70632
|
entity |
| Predicate | occasionalRange |
P47451
|
FINISHED |
| Object | subantarctic islands |
—
|
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: subantarctic islands | Statement: [leopard seal, occasionalRange, subantarctic islands]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: occasionalRange Context triple: [leopard seal, occasionalRange, subantarctic islands]
-
A.
typicalRange
Indicates the usual or expected range of values, conditions, or states within which something normally occurs or applies.
-
B.
rangeRestricted
Indicates that the relationship or action applies only within a specified, limited subset of a broader domain or scope.
-
C.
usedBetween
Indicates that something serves as a means, medium, or shared resource connecting or operating jointly between two entities.
-
D.
range
Indicates that a value, property, or effect extends between specified limits or over a specified interval or scope.
-
E.
occursOnOrAround
Indicates that an event or action takes place on a specific date or within a small, approximate time window surrounding that date.
- F. None of above. chosen
Provenance (4 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_69ad85a660c48190998489309a3b4869 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb244435c81908e35d2aa36ec4f46 |
completed | March 8, 2026, 5:30 p.m. |
| PD | Predicate disambiguation | batch_69ada42fbe7c8190b9f185b5ab985f17 |
completed | March 8, 2026, 4:30 p.m. |
| PDg | Predicate description generation | batch_69ada52716ec81908e89688a81039394 |
completed | March 8, 2026, 4:34 p.m. |
Created at: March 8, 2026, 3:13 p.m.