Triple
T26169220
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tinakula |
E654349
|
entity |
| Predicate | risesDirectlyFrom |
P160002
|
FINISHED |
| Object | sea |
—
|
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: sea | Statement: [Tinakula, risesDirectlyFrom, sea]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: risesDirectlyFrom Context triple: [Tinakula, risesDirectlyFrom, sea]
-
A.
risesOn
Indicates that one entity ascends, increases, or moves upward in position, level, or value relative to another reference point or context.
-
B.
risesIn
Indicates that a river or similar watercourse originates or begins its flow in a specified location.
-
C.
raisedFrom
Indicates that one entity has been elevated, derived, or brought up from another prior state, source, or condition.
-
D.
isStartingPointOf
Indicates that something serves as the initial point or origin from which another thing, process, or path begins.
-
E.
ascendedTo
Indicates that one entity rose, climbed, or moved upward to reach the position, level, or location of another entity.
- 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_69ee5b44391c81908bdbd8813ba9aa99 |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f60c4132a88190ba74c1c290cbe35d |
completed | May 2, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69f5b0021da88190bdd4cf2698c23edf |
completed | May 2, 2026, 8:04 a.m. |
| PDg | Predicate description generation | batch_69f5f6b32a8881909baa0db57b80d56a |
completed | May 2, 2026, 1:05 p.m. |
Created at: April 26, 2026, 8:34 p.m.