Triple
T37800776
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moray |
E942367
|
entity |
| Predicate | largestDepth |
P968
|
FINISHED |
| Object | about 30 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: about 30 meters | Statement: [Moray, largestDepth, about 30 meters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: largestDepth Context triple: [Moray, largestDepth, about 30 meters]
-
A.
maximumDepth
chosen
Indicates the greatest extent or deepest level reached by something within a given context or structure.
-
B.
maxDepthLocation
Indicates the location at which the maximum depth of something (e.g., an object, structure, or feature) is reached or measured.
-
C.
maximumDepthCharacteristic
Indicates the greatest depth value that characterizes or constrains the extent of something (such as an object, layer, or feature).
-
D.
isDeepest
Indicates that one entity has the greatest depth relative to a specified reference or set of comparable entities.
-
E.
hasMaximumDepth
Indicates that an entity possesses a greatest or limiting depth value beyond which it does not extend.
- 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_69f76ee6f1f4819091e2cf9c9e6aee19 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fcc4b700748190ae00b21d09c96695 |
completed | May 7, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69fcb0f9d3d881908a049475182fb039 |
completed | May 7, 2026, 3:34 p.m. |
Created at: May 3, 2026, 4:19 p.m.