Triple
T29068150
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chencho Corleone |
E735741
|
entity |
| Predicate | collaborationLanguage |
P166293
|
FINISHED |
| Object | Spanish |
—
|
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: Spanish | Statement: [Chencho Corleone, collaborationLanguage, Spanish]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: collaborationLanguage Context triple: [Chencho Corleone, collaborationLanguage, Spanish]
-
A.
usesWorkingLanguagesOf
Indicates that one entity employs or operates using the working languages associated with another entity.
-
B.
coAuthorOfLanguage
Indicates that two or more entities jointly authored, designed, or created a particular language.
-
C.
coexistsWithLanguage
Indicates that one entity exists or functions alongside a particular language at the same time, without excluding or replacing it.
-
D.
sharesLanguageWith
Indicates that two entities use at least one common language for communication.
-
E.
isWorkingLanguageOf
Indicates that a particular language is officially used as a medium of work, communication, or operation within a specified organization, institution, or context.
- 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_69f077e9b0a48190bb79548279cb7f64 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f660f7d5748190821e550b26a68eda |
completed | May 2, 2026, 8:39 p.m. |
| PD | Predicate disambiguation | batch_69f65c2376a08190be5215171e908e69 |
completed | May 2, 2026, 8:18 p.m. |
| PDg | Predicate description generation | batch_69f65f75ac608190a62cd6afce14f68e |
completed | May 2, 2026, 8:32 p.m. |
Created at: April 28, 2026, 10:19 a.m.