Triple
T21519791
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brünnich's guillemot |
E530941
|
entity |
| Predicate | canDiveToDepth |
P58244
|
FINISHED |
| Object | over 100 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: over 100 meters | Statement: [Brünnich's guillemot, canDiveToDepth, over 100 meters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canDiveToDepth Context triple: [Brünnich's guillemot, canDiveToDepth, over 100 meters]
-
A.
hasDivingDepth
Indicates that an entity is associated with a specific depth to which it can or does dive.
-
B.
hasDeepDivingAbility
Indicates that an entity possesses the capability to dive to significant depths, typically beyond normal or shallow diving limits.
-
C.
hasDiveDifficulty
Indicates that an action or event of diving is associated with a specified level of difficulty.
-
D.
hasDivingComponent
Indicates that an activity, event, or process includes or involves a diving-related element or action.
-
E.
maximumDiveDepth
chosen
Indicates the greatest depth below the surface that an entity is capable of or allowed to dive.
- 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_69e0c45d95a081908e7962ad215da746 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ee884af0f08190bc1f3d70e57a325d |
completed | April 26, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69e6320043bc81909417c41a718652ba |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:26 p.m.