Triple
T27234827
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Broken Ear |
E682244
|
entity |
| Predicate | languageOfFirstSerialization |
P192632
|
FINISHED |
| Object | French |
—
|
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: French | Statement: [The Broken Ear, languageOfFirstSerialization, French]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageOfFirstSerialization Context triple: [The Broken Ear, languageOfFirstSerialization, French]
-
A.
languageOfPrimaryCompilation
Indicates the programming or source language in which an entity was primarily compiled.
-
B.
derivationLanguage
Indicates the language from which something (such as a word, term, or expression) is derived.
-
C.
primaryLanguageVersion
Indicates that one language version of a resource is designated as the main or default version among its language variants.
-
D.
languageOfPrimaryOutput
Indicates the language in which the primary output or main result of an entity (such as a work, process, or system) is expressed.
-
E.
languageOfNotation
Indicates the language in which a given notation, script, or symbolic system is expressed or encoded.
- 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_69eefacdad7881908b7bca61c90a1a1e |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69fd231cab588190ad0953dc8f4af8f2 |
completed | May 7, 2026, 11:41 p.m. |
| PD | Predicate disambiguation | batch_69fd1aa3f1c481909fe6e9cab1383551 |
completed | May 7, 2026, 11:05 p.m. |
| PDg | Predicate description generation | batch_69fd231bdd108190900369e07c854e95 |
completed | May 7, 2026, 11:41 p.m. |
Created at: April 27, 2026, 9:47 a.m.