Triple
T26484477
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tillamook Head |
E664782
|
entity |
| Predicate | dateOfHistoricVisit |
P106239
|
FINISHED |
| Object | January 1806 |
—
|
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: January 1806 | Statement: [Tillamook Head, dateOfHistoricVisit, January 1806]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateOfHistoricVisit Context triple: [Tillamook Head, dateOfHistoricVisit, January 1806]
-
A.
visitedDate
Indicates the specific date on which one entity visited or was present at another entity or location.
-
B.
historicalPresence
Indicates that an entity existed, was active, or had a notable presence in a particular place or context during a past time period.
-
C.
lastVisitedByHumans
Indicates that the referenced place or object was most recently visited or physically accessed by humans.
-
D.
dateOfHistoricalAssociation
chosen
Indicates the specific date or time period during which a notable historical association, connection, or event between entities took place.
-
E.
bestVisitedAt
Indicates the optimal time or conditions under which a place or entity should be visited.
- 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_69ee883bc85481909885f92415cbce33 |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f67257b0448190a13011af81c81449 |
completed | May 2, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69f66ec3d3d48190ab2f2b71939e572e |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 27, 2026, 12:29 a.m.