Triple
T24857923
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | La secta del Fénix |
E622076
|
entity |
| Predicate | incluidoEn |
P56991
|
FINISHED |
| Object | ediciones recopilatorias de cuentos de Borges |
—
|
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: ediciones recopilatorias de cuentos de Borges | Statement: [La secta del Fénix, incluidoEn, ediciones recopilatorias de cuentos de Borges]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: incluidoEn Context triple: [La secta del Fénix, incluidoEn, ediciones recopilatorias de cuentos de Borges]
-
A.
includedBy
chosen
Indicates that one entity is contained within, encompassed by, or treated as a subset or member of another entity.
-
B.
includes
Indicates that one entity contains, encompasses, or has another entity as a part, member, or subset.
-
C.
aimedToInclude
Indicates that one entity intentionally sought to have another entity or element contained or incorporated within it.
-
D.
includedWith
Indicates that one entity is provided or packaged together as part of another entity.
-
E.
containedPartOf
Indicates that one entity is physically or logically included within and forms a part of another 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_69e2fac350d08190b3affde1b451a8c5 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f657f653448190a945b4751af8507d |
completed | May 2, 2026, 8 p.m. |
| PD | Predicate disambiguation | batch_69f6575ba12081909396036f78757a76 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 18, 2026, 5:21 a.m.