Triple
T35790719
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tic Tac (UFO) |
E1034684
|
entity |
| Predicate | observedOffCoastOf |
P15643
|
FINISHED |
| Object | Southern California |
—
|
NE NERFINISHED |
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: Southern California | Statement: [Tic Tac (UFO), observedOffCoastOf, Southern California]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: observedOffCoastOf Context triple: [Tic Tac (UFO), observedOffCoastOf, Southern California]
-
A.
coastOff
chosen
Indicates that one entity is located just off the coast of another, typically in nearby offshore waters rather than directly on the shoreline.
-
B.
spokenOffCoastOf
Indicates that a language or speech variety is used or heard in areas located off the coast of a particular place, typically on nearby islands or maritime regions.
-
C.
visibilityFromShore
Indicates that something can be seen or is visually detectable from the shoreline or coast.
-
D.
navigatedAlongCoastOf
Indicates that an entity traveled or steered a course following the coastline of another geographic entity.
-
E.
connectsToCoastAt
Indicates that one entity has a direct physical or geographical connection or access to a coastline at the location of another entity.
- 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_69f76e1575908190aaa306d843b41c14 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7be53890081909b1d93f30a8f31c6 |
completed | May 3, 2026, 9:29 p.m. |
| PD | Predicate disambiguation | batch_69f7bccacbac8190978976324c67db28 |
completed | May 3, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:06 p.m.