Triple
T38156465
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Virgen de la Caridad del Cobre |
E952899
|
entity |
| Predicate | hasCanonicalCrown |
P202105
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Virgen de la Caridad del Cobre, hasCanonicalCrown, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCanonicalCrown Context triple: [Virgen de la Caridad del Cobre, hasCanonicalCrown, yes]
-
A.
hasCrownStructure
Indicates that one entity possesses or exhibits a particular crown-like structural feature in relation to another entity or context.
-
B.
hasCanonicalCoronationStatus
Indicates that an entity has an officially recognized or standard status with respect to a coronation.
-
C.
hasCrownName
Indicates that an entity possesses or is identified by a specific crown name, typically used as an official or regal title.
-
D.
hasCrownGroup
Indicates that an entity belongs to, or is classified within, the crown group (the clade consisting of a common ancestor and all its living descendants) of another specified lineage or taxonomic group.
-
E.
hasCrownCount
Indicates the number of crowns that an entity possesses or is associated with.
- F. None of above. chosen
Provenance (4 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_69f76f0a67f4819080c492f61d688fcc |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a00512437d48190ad20324968ead5f4 |
completed | May 10, 2026, 9:34 a.m. |
| PD | Predicate disambiguation | batch_6a0050227350819099f41369c3d168be |
completed | May 10, 2026, 9:30 a.m. |
| PDg | Predicate description generation | batch_6a0051234cc08190adae6e2cfae2f8cc |
completed | May 10, 2026, 9:34 a.m. |
Created at: May 3, 2026, 4:21 p.m.