Triple
T8291850
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | McHenry Papers |
E193916
|
entity |
| Predicate | relatesToRole |
P4342
|
FINISHED |
| Object | Founding Father of the United States |
—
|
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 of the United States | Statement: [McHenry Papers, relatesToRole, Founding Father of the United States]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatesToRole Context triple: [McHenry Papers, relatesToRole, Founding Father of the United States]
-
A.
refersToRole
chosen
Indicates that one entity designates, mentions, or points to another entity specifically in its capacity as a role or position.
-
B.
hasRelativeRole
Indicates that one entity holds a familial or kinship-based role in relation to another entity.
-
C.
connectsRole
Indicates a relationship in which one entity is linked to another by assigning or associating a specific role between them.
-
D.
termRelationTo
Indicates a general relational association between one term and another, without specifying the exact nature of that relationship.
-
E.
identityRelation
Indicates that two entities are in fact the very same entity, not merely similar or equivalent.
- 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_69ca82e32db481908b72f3804fa71152 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7c9ccbfc81908825685c23b80d23 |
completed | March 31, 2026, 7:49 a.m. |
| PD | Predicate disambiguation | batch_69cb70b5b5348190b296e0ecec95de60 |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 5:52 p.m.