Triple
T28534233
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Banana Reef |
E722117
|
entity |
| Predicate | approximateMaxDepth |
P9310
|
FINISHED |
| Object | 30 metres |
—
|
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: 30 metres | Statement: [Banana Reef, approximateMaxDepth, 30 metres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateMaxDepth Context triple: [Banana Reef, approximateMaxDepth, 30 metres]
-
A.
hasApproximateDepth
chosen
Indicates that an entity is associated with a depth value that is not exact but estimated or approximate.
-
B.
maximumDepth
Indicates the greatest extent or deepest level reached by something within a given context or structure.
-
C.
hasMaximumDepth
Indicates that an entity possesses a greatest or limiting depth value beyond which it does not extend.
-
D.
approximateMaximumHeight
Indicates the estimated upper limit of an entity’s height, rather than an exact measured value.
-
E.
hasUnknownMaximumDepth
Indicates that the maximum depth associated with an entity or process is not known or cannot be determined.
- 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_69f01a5d7ec88190ada2d5be7c06c35d |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69fd2a215d6c8190a1a428ccaee603f1 |
completed | May 8, 2026, 12:11 a.m. |
| PD | Predicate disambiguation | batch_69fd28ef19688190bb8370f2812a43e7 |
completed | May 8, 2026, 12:06 a.m. |
Created at: April 28, 2026, 3:31 a.m.