Triple
T6327989
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Difference Engine |
E141904
|
entity |
| Predicate | languageOfDesignDocuments |
P42636
|
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: [Difference Engine, languageOfDesignDocuments, English]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageOfDesignDocuments Context triple: [Difference Engine, languageOfDesignDocuments, English]
-
A.
languageOfDocumentation
chosen
Indicates the language in which the documentation for an entity is written or provided.
-
B.
languageDesigned
Indicates that one entity created or developed the language used or associated with another entity.
-
C.
languageOfRecords
Indicates the language in which the records are written or maintained.
-
D.
languageProvision
Indicates that one entity supplies, supports, or makes available a particular language (or set of languages) for use by another entity.
-
E.
languageFamilyDocumented
Indicates that there exists documentation or records describing the language family to which the entity’s language belongs.
- 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_69c008d201748190917e69c41ba3f978 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c064e9532081908277f10ec380a486 |
completed | March 22, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69c060e7e2d48190af9d004236466788 |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:29 p.m.