Triple
T21711221
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John W. Fithian |
E535909
|
entity |
| Predicate | hasLocalProminence |
P9790
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [John W. Fithian, hasLocalProminence, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLocalProminence Context triple: [John W. Fithian, hasLocalProminence, true]
-
A.
hasProminence
chosen
Indicates that one entity stands out in importance, visibility, or influence relative to others within a given context.
-
B.
hasMinimumProminence
Indicates that an entity meets or exceeds a specified threshold level of prominence or importance within a given context.
-
C.
elevatedInProminenceBy
Indicates that an entity’s prominence, status, or visibility is increased as a result of the actions or influence of another entity.
-
D.
hasRelativeProminenceComparedTo
Indicates that one entity has a greater, lesser, or otherwise specified level of prominence or importance when compared to another entity.
-
E.
hasProminentLocation
Indicates that an entity occupies a highly visible, central, or otherwise notable position within a given space or context.
- 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_69e0c46b44c0819088ab883ebd44e0e8 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69efb5333c8481909d729fb3bc3c9bc5 |
completed | April 27, 2026, 7:12 p.m. |
| PD | Predicate disambiguation | batch_69e6969725bc81908e7ad19619ba2688 |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:46 p.m.