Triple
T5477309
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Posidonia oceanica meadows |
E123387
|
entity |
| Predicate | foundAtDepth |
P36777
|
FINISHED |
| Object | 1–40 meters |
—
|
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: 1–40 meters | Statement: [Posidonia oceanica meadows, foundAtDepth, 1–40 meters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foundAtDepth Context triple: [Posidonia oceanica meadows, foundAtDepth, 1–40 meters]
-
A.
reachedDepth
Indicates that an entity has arrived at or attained a specified depth level in some medium or context.
-
B.
maxDepthLocation
Indicates the location at which the maximum depth of something (e.g., an object, structure, or feature) is reached or measured.
-
C.
hasDepth
chosen
Indicates that an entity possesses a measurable extent or distance from its surface inward or from top to bottom.
-
D.
testDepth
Indicates that an entity is evaluated or measured based on how deep or thorough it is, often in terms of levels, layers, or extent below a surface or baseline.
-
E.
maximumDepth
Indicates the greatest extent or deepest level reached by something within a given context or structure.
- 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_69bd4648883481909e9775d43300c5fa |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd92460f008190bf9d64ddd9c507a7 |
completed | March 20, 2026, 6:30 p.m. |
| PD | Predicate disambiguation | batch_69bd91a58c448190904964a439045e05 |
completed | March 20, 2026, 6:27 p.m. |
Created at: March 20, 2026, 2:09 p.m.