Triple
T27053378
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Datapoint 2200 |
E684837
|
entity |
| Predicate | programmableIn |
P31541
|
FINISHED |
| Object | assembly language |
—
|
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: assembly language | Statement: [Datapoint 2200, programmableIn, assembly language]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: programmableIn Context triple: [Datapoint 2200, programmableIn, assembly language]
-
A.
programmability
Indicates that an entity can be configured, controlled, or modified through programming or code to change its behavior or functions.
-
B.
programmedVia
chosen
Indicates that one entity is created, configured, or made to operate through the use of another entity as its programming method, tool, or medium.
-
C.
programmableTypeUses
Indicates that one programmable type makes use of, depends on, or incorporates another type in its implementation or behavior.
-
D.
possiblePrograms
Indicates that there exist one or more programs that could potentially be applicable, valid, or chosen in relation to the given entities or context.
-
E.
implementedProgram
Indicates that an entity has created, developed, or put into operation a particular program or software system.
- 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_69ef14829fac8190914bef9ecc3005d7 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f661b58ac48190907b6c6e9ccc2c59 |
completed | May 2, 2026, 8:42 p.m. |
| PD | Predicate disambiguation | batch_69f660eea4648190b0d5e24293607813 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 27, 2026, 8:15 a.m.