Triple
T18655501
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cathlamet |
E456052
|
entity |
| Predicate | timeOfNotableContact |
P132167
|
FINISHED |
| Object | early 19th century |
—
|
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: early 19th century | Statement: [Cathlamet, timeOfNotableContact, early 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeOfNotableContact Context triple: [Cathlamet, timeOfNotableContact, early 19th century]
-
A.
timeOfLossOfContactUTC
Indicates the specific time, expressed in Coordinated Universal Time (UTC), at which contact with an entity was lost.
-
B.
timePeriodOfNotableBearer
Indicates the span of time during which a notable bearer is recognized as having held, embodied, or been associated with the subject.
-
C.
historicalContactWith
Indicates that two entities have interacted or been in communication with each other at some point in the past.
-
D.
notableEventTime
Indicates the specific time at which a notable or significant event occurred.
-
E.
locationOfLastContact
Indicates the place where the most recent interaction or communication with the referenced entity occurred.
- F. None of above. chosen
Provenance (4 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_69d8d38ea1e88190997e9b231190ba6f |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e55084012881909b9dd60565011c86 |
completed | April 19, 2026, 10 p.m. |
| PD | Predicate disambiguation | batch_69e478d85864819093cbad5ed9b54878 |
completed | April 19, 2026, 6:40 a.m. |
| PDg | Predicate description generation | batch_69e484133ee48190a80f1889d79f34c9 |
completed | April 19, 2026, 7:28 a.m. |
Created at: April 10, 2026, 11:47 a.m.