Triple
T5891550
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Askernish |
E131000
|
entity |
| Predicate | golfCourseFounded |
P4025
|
FINISHED |
| Object | 1891 |
—
|
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: 1891 | Statement: [Askernish, golfCourseFounded, 1891]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: golfCourseFounded Context triple: [Askernish, golfCourseFounded, 1891]
-
A.
secondClubFounded
Indicates that an entity is the second club established by or associated with another entity (such as a person, organization, or institution).
-
B.
foundedOn
Indicates that an entity was established, created, or brought into existence on a specific date or point in time.
-
C.
foundedAs
Indicates the original name or form under which an organization, institution, or entity was first established.
-
D.
wasFoundedBy
Indicates that an organization, institution, or entity came into existence through the initiating action or establishment by a specific founder or founding group.
-
E.
foundedAt
chosen
Indicates the time or date at which an entity (such as an organization, project, or institution) was established or created.
- 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_69c00857439c819095950754176aa58a |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c03fe07b7081909f8577ec3a9a1a8d |
completed | March 22, 2026, 7:15 p.m. |
| PD | Predicate disambiguation | batch_69c0334bdc308190ad0d7199ab975588 |
completed | March 22, 2026, 6:22 p.m. |
Created at: March 22, 2026, 3:58 p.m.