Triple
T28019221
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | common loon |
E707638
|
entity |
| Predicate | divingDepth |
P58244
|
FINISHED |
| Object | can dive more than 60 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: can dive more than 60 meters | Statement: [common loon, divingDepth, can dive more than 60 meters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: divingDepth Context triple: [common loon, divingDepth, can dive more than 60 meters]
-
A.
hasDivingDepth
Indicates that an entity is associated with a specific depth to which it can or does dive.
-
B.
maximumDiveDepth
chosen
Indicates the greatest depth below the surface that an entity is capable of or allowed to dive.
-
C.
hasDiveDifficulty
Indicates that an action or event of diving is associated with a specified level of difficulty.
-
D.
diveHeight
Indicates the vertical distance from which a dive is initiated or performed.
-
E.
hasDeepDivingAbility
Indicates that an entity possesses the capability to dive to significant depths, typically beyond normal or shallow diving limits.
- 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_69ef96baf3a881909a2b63844185dddd |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f643ed0b7481908cf25f3afec0a61d |
completed | May 2, 2026, 6:35 p.m. |
| PD | Predicate disambiguation | batch_69f641def1e88190a05bf865ced78b23 |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 27, 2026, 8:09 p.m.