Triple
T8070221
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FAT |
E188350
|
entity |
| Predicate | namingRationale |
P7885
|
FINISHED |
| Object | proximity to Yosemite National Park |
—
|
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: proximity to Yosemite National Park | Statement: [FAT, namingRationale, proximity to Yosemite National Park]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: namingRationale Context triple: [FAT, namingRationale, proximity to Yosemite National Park]
-
A.
reasonForName
chosen
Indicates the explanation or cause behind why an entity has a particular name.
-
B.
namingBasis
Indicates that one entity serves as the reason, source, or criterion for how another entity is named or designated.
-
C.
isNamedFor
Indicates that one entity bears its name in honor of, or derived from, another entity.
-
D.
namedFeature
Indicates that an entity has a specific feature or attribute that is explicitly given a name.
-
E.
reasonForEpithet
Indicates the cause, motivation, or circumstance that explains why a particular epithet is applied to an 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_69ca82b42674819086840efea12478e5 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3ffe29188190834ec4f71043a99d |
completed | March 31, 2026, 3:31 a.m. |
| PD | Predicate disambiguation | batch_69cb049cd51c8190bb3b0f503e42fa8d |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:27 p.m.