Triple
T23877485
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Heavens are Telling |
E592907
|
entity |
| Predicate | commonPerformanceLanguage |
P43093
|
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 Heavens are Telling, commonPerformanceLanguage, English]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonPerformanceLanguage Context triple: [The Heavens are Telling, commonPerformanceLanguage, English]
-
A.
hasTypicalPerformanceLanguage
Indicates that an entity is commonly or characteristically expressed, implemented, or described using a particular programming or specification language.
-
B.
performedLanguage
chosen
Indicates that an action, work, or performance was carried out using a specified language.
-
C.
typicalLanguages
Indicates the languages that are commonly or characteristically used, spoken, or associated with a given entity.
-
D.
shareMajorLanguage
Indicates that the entities have at least one primary or major language in common.
-
E.
languagesUsed
Indicates that one entity uses, employs, or is expressed in one or more languages associated with the other 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_69e25d23a5c88190ae3999c70ca15e08 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1cc02277c8190b0c15d6525f3b38d |
completed | April 29, 2026, 9:14 a.m. |
| PD | Predicate disambiguation | batch_69f1614a65a88190bde1efb368a151e4 |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 8:15 p.m.