Triple
T22748113
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Monad Shoal |
E562609
|
entity |
| Predicate | typicalDiveType |
P47039
|
FINISHED |
| Object | boat dive |
—
|
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: boat dive | Statement: [Monad Shoal, typicalDiveType, boat dive]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalDiveType Context triple: [Monad Shoal, typicalDiveType, boat dive]
-
A.
hasDiveType
chosen
Indicates that an entity performs or is associated with a specific type or category of dive.
-
B.
hasDiveDifficulty
Indicates that an action or event of diving is associated with a specified level of difficulty.
-
C.
divingBehavior
Indicates the characteristic way an entity performs or exhibits diving actions, such as how, when, or how often it dives.
-
D.
hasDivingDepth
Indicates that an entity is associated with a specific depth to which it can or does dive.
-
E.
hasDivingComponent
Indicates that an activity, event, or process includes or involves a diving-related element or action.
- 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_69e245513a5c81908d5cb471b4fc429d |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f179b702388190b134dde5f80ea3cd |
completed | April 29, 2026, 3:23 a.m. |
| PD | Predicate disambiguation | batch_69eed2b88d88819096015deb6a648801 |
completed | April 27, 2026, 3:06 a.m. |
Created at: April 17, 2026, 3:24 p.m.