Triple
T3302896
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Petoskey stones |
E69375
|
entity |
| Predicate | officialStatusStartDate |
P6938
|
FINISHED |
| Object | 1965 |
—
|
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: 1965 | Statement: [Petoskey stones, officialStatusStartDate, 1965]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: officialStatusStartDate Context triple: [Petoskey stones, officialStatusStartDate, 1965]
-
A.
designationDate
chosen
Indicates the date on which an entity is formally assigned, designated, or given a particular status or role.
-
B.
establishedFrom
Indicates that something was created, founded, or formed starting from a specified source, origin, or prior entity.
-
C.
ordinationDate
Indicates the date on which an individual was formally ordained to a religious office or role.
-
D.
candidacyStartDate
Indicates the date on which an entity’s candidacy for a role, position, or election officially begins.
-
E.
establishedAt
Indicates the specific time or date at which something (such as an organization, system, or entity) was founded or brought into existence.
- 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_69ad859e529c8190a404273f53cb487d |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb0a9450481909f0d630e5593085e |
completed | March 8, 2026, 5:23 p.m. |
| PD | Predicate disambiguation | batch_69ada42625308190be257f16a623a410 |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:11 p.m.