Triple
T315442
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Singing Fool |
E7694
|
entity |
| Predicate | languageOfSong |
P8513
|
FINISHED |
| Object | English |
—
|
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: English | Statement: [The Singing Fool, languageOfSong, English]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageOfSong Context triple: [The Singing Fool, languageOfSong, English]
-
A.
languageOfExpression
chosen
Indicates that a particular language is used as the medium or form in which an expression (such as a text, utterance, or work) is realized.
-
B.
languageCodeISO639-1
Indicates that the subject entity is associated with the specified two-letter ISO 639-1 language code.
-
C.
primaryLanguageOf
Indicates that a specified language is the main or official language used by a particular entity (such as a person, organization, or region).
-
D.
isLanguageOf
Indicates that a particular language is used as the official or primary language associated with a given entity (such as a person, document, or region).
-
E.
languageCodeISO639-2
Indicates that an entity is associated with a language identified by its ISO 639-2 three-letter code.
- 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_69a2e7e7af7881908890039d6be4e9b8 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ea6462148190825acc57f6d2adaf |
completed | Feb. 28, 2026, 1:15 p.m. |
| PD | Predicate disambiguation | batch_69a2e9428098819089d5950cd2c96dc4 |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.