Triple
T11558831
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bryc |
E274082
|
entity |
| Predicate | derivedFrom |
P909
|
FINISHED |
| Object | Bryce |
E52780
|
NE 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: Bryce | Statement: [Bryc, derivedFrom, Bryce]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bryce Context triple: [Bryc, derivedFrom, Bryce]
-
A.
Bryce
chosen
Bryce is a masculine given name commonly used in English-speaking countries.
-
B.
Bryce Point
Bryce Point is a popular scenic overlook in Bryce Canyon National Park known for its expansive views of the park’s distinctive hoodoos and amphitheaters.
-
C.
La Quiaca
La Quiaca is a small Argentine border city in the far north of Jujuy Province, known as a key crossing point into Bolivia.
-
D.
Conder
Conder is a residential suburb located in the district of Tuggeranong in Canberra, Australian Capital Territory.
-
E.
Bryce, Utah
Bryce, Utah is a small gateway town in southern Utah that serves as the primary access point and service hub for visitors to Bryce Canyon National Park.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d6aae4dfa48190a3ab0b19a159a3c5 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d88a888e8481909386009b9603e4d3 |
completed | April 10, 2026, 5:28 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ee86b56e4081908746bb3355f6ec47 |
completed | April 26, 2026, 9:42 p.m. |
Created at: April 8, 2026, 9:37 p.m.