Triple
T27714982
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clymer, Pennsylvania |
E698791
|
entity |
| Predicate | hasNamedForOccupation |
P117536
|
FINISHED |
| Object | Founding Father |
—
|
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: Founding Father | Statement: [Clymer, Pennsylvania, hasNamedForOccupation, Founding Father]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNamedForOccupation Context triple: [Clymer, Pennsylvania, hasNamedForOccupation, Founding Father]
-
A.
isNamedAfterOccupation
Indicates that an entity’s name is derived from or based on a particular occupation or profession.
-
B.
occupationalNameFor
Indicates that one entity is the name or label used to denote the occupation or profession of another entity.
-
C.
isOccupationalSurname
Indicates that a surname originates from or is derived from a person’s occupation or trade.
-
D.
namedAfterOccupationOrRole
chosen
Indicates that an entity is named after a specific occupation, profession, or social role associated with a person or group.
-
E.
hasOccupationOfDesignee
Indicates that one entity serves as the designated or appointed holder of an occupation or role for 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_69ef590f655c81909f93893b3b3219b2 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f7c29e1b848190b945c6c6120a5330 |
completed | May 3, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69f7c1b6e7a881908deb96bedb2713f4 |
completed | May 3, 2026, 9:44 p.m. |
Created at: April 27, 2026, 3:04 p.m.