Triple
T34208204
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grand Ridge (local topographic feature) |
E877574
|
entity |
| Predicate | namedByRelation |
P136469
|
FINISHED |
| Object | namesake of Grand Ridge, Illinois |
—
|
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: namesake of Grand Ridge, Illinois | Statement: [Grand Ridge (local topographic feature), namedByRelation, namesake of Grand Ridge, Illinois]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: namedByRelation Context triple: [Grand Ridge (local topographic feature), namedByRelation, namesake of Grand Ridge, Illinois]
-
A.
namedForRelationship
chosen
Indicates that one entity serves as the namesake or source of the name for another entity.
-
B.
namedAs
Indicates that one entity is given, known by, or referred to using the name of another entity.
-
C.
isRelatedName
Indicates that one name is connected to another through a variant, derivative, or otherwise non-identical but related naming relationship.
-
D.
pairedWithRelationshipName
Indicates that one entity is associated with another as a named pair within a specific relationship context.
-
E.
valueRelation
Indicates a comparative or associative relationship between the values or magnitudes of two or more entities.
- 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_69f349aff5f0819096275315abea5344 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fcd867f36081908c88c55a6a1404c1 |
completed | May 7, 2026, 6:22 p.m. |
| PD | Predicate disambiguation | batch_69fcd1f47b188190b4cf4b4c748d9d03 |
completed | May 7, 2026, 5:55 p.m. |
Created at: May 1, 2026, 1:55 a.m.