Triple
T1827253
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A Brief History of Time |
E40679
|
entity |
| Predicate | hasBeenTranslatedIntoManyLanguages |
P2303
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [A Brief History of Time, hasBeenTranslatedIntoManyLanguages, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBeenTranslatedIntoManyLanguages Context triple: [A Brief History of Time, hasBeenTranslatedIntoManyLanguages, yes]
-
A.
wroteInMultipleLanguages
Indicates that an entity authored written works using more than one language.
-
B.
estimatedNumberOfLanguages
Indicates the approximate count of distinct languages associated with an entity, typically based on estimation rather than an exact measurement.
-
C.
hasApproximateNumberOfLanguages
Indicates that an entity is associated with a quantity representing an estimated or non-exact count of languages.
-
D.
hasTranslation
chosen
Indicates that one entity is a translation or translated version of another entity in a different language.
-
E.
isBilingual
Indicates that an entity is able to communicate fluently in two distinct languages.
- 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_69a8864644bc8190b2358ab897194ac1 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb45402688190b9a535b14030c354 |
completed | March 7, 2026, 5:15 a.m. |
| PD | Predicate disambiguation | batch_69abafd6a9948190ac2b2743db6f8f69 |
completed | March 7, 2026, 4:55 a.m. |
Created at: March 4, 2026, 7:32 p.m.