Triple
T26035249
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | San Ignacio Lagoon |
E647532
|
entity |
| Predicate | notableBehaviorObserved |
P23475
|
FINISHED |
| Object | gray whales approaching boats |
—
|
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: gray whales approaching boats | Statement: [San Ignacio Lagoon, notableBehaviorObserved, gray whales approaching boats]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableBehaviorObserved Context triple: [San Ignacio Lagoon, notableBehaviorObserved, gray whales approaching boats]
-
A.
behaviorObserved
chosen
Indicates that a particular behavior or action has been witnessed, recorded, or detected in relation to an entity or context.
-
B.
observationNote
Indicates that there is an associated free-text comment or remark providing additional details or context about an observation.
-
C.
notableImpression
Indicates that one entity has made a significant or memorable impact on another entity.
-
D.
observationBenefit
Indicates that one entity gains an advantage, insight, or positive outcome as a result of observing another entity or phenomenon.
-
E.
notableDuring
Indicates that something was especially prominent, active, or significant during a particular time period or event.
- 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_69e77e8c88f08190858c4c81bd2e1b9a |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69fe1fd637c08190aa95cd2478c278cb |
completed | May 8, 2026, 5:39 p.m. |
| PD | Predicate disambiguation | batch_69fe19344bb481909b5e2144155e4add |
completed | May 8, 2026, 5:11 p.m. |
Created at: April 22, 2026, 9:07 a.m.