Triple
T17387000
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cíbola |
E422711
|
entity |
| Predicate | associatedLegendType |
P1582
|
FINISHED |
| Object | treasure legend |
—
|
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: treasure legend | Statement: [Cíbola, associatedLegendType, treasure legend]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedLegendType Context triple: [Cíbola, associatedLegendType, treasure legend]
-
A.
hasLegendAssociatedWith
chosen
Indicates that something is connected to or accompanied by a traditional story, myth, or legend.
-
B.
legendStatus
Indicates that an entity holds, is assigned, or is associated with a particular legend-related status or classification.
-
C.
regionOfLegend
Indicates the geographic area or locale with which a particular legend or myth is associated.
-
D.
legend
Indicates that an entity is a traditional or historical story, figure, or narrative widely regarded as legendary rather than strictly factual.
-
E.
instrumentInLegend
Indicates that an instrument is featured or plays a role within a legend or mythological narrative.
- 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_69d889d710288190bf0f4762801fefae |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e43a8a93f48190a31f5cc58d950758 |
completed | April 19, 2026, 2:14 a.m. |
| PD | Predicate disambiguation | batch_69e3b02ac8688190a7182f1b2151d721 |
completed | April 18, 2026, 4:24 p.m. |
Created at: April 10, 2026, 5:45 a.m.