Triple
T7476750
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Justin Smith Morrill |
E176649
|
entity |
| Predicate | viafID |
P76473
|
FINISHED |
| Object | 4924573 |
—
|
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: 4924573 | Statement: [Justin Smith Morrill, viafID, 4924573]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: viafID Context triple: [Justin Smith Morrill, viafID, 4924573]
-
A.
ISNI
Indicates that an entity is associated with a specific International Standard Name Identifier, uniquely identifying its public identity in creative or scholarly activities.
-
B.
identifierFor
Indicates that one entity serves as a unique identifying label or code for another entity.
-
C.
issuerAlsoKnownFor
Indicates that the issuer is additionally recognized or notable for another role, activity, or attribute beyond their primary identified capacity.
-
D.
relatedIdentifier
Indicates that one identifier is associated with another identifier that refers to the same or a related entity in a different context or system.
-
E.
notableCulturalFigure
Indicates that a person holds significant influence or recognition within a culture’s arts, traditions, values, or public life.
- 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_69c69f236ce08190a04d7679f03b29b2 |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f4ee23d081908e05658a651661fc |
completed | March 27, 2026, 9:21 p.m. |
| PD | Predicate disambiguation | batch_69c6f03d967081908a8e696ff9693b90 |
completed | March 27, 2026, 9:01 p.m. |
| PDg | Predicate description generation | batch_69c6f105e320819091db3cdb1f1351f0 |
completed | March 27, 2026, 9:05 p.m. |
Created at: March 27, 2026, 3:41 p.m.