Triple
T2313538
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BCPL |
E51010
|
entity |
| Predicate | implementationStrategy |
P13064
|
FINISHED |
| Object | portable compiler with intermediate 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: portable compiler with intermediate language | Statement: [BCPL, implementationStrategy, portable compiler with intermediate language]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: implementationStrategy Context triple: [BCPL, implementationStrategy, portable compiler with intermediate language]
-
A.
implementedPolicy
Indicates that a particular policy has been put into effect or carried out by an entity.
-
B.
implementationStatus
Indicates the current state or progress of carrying out or realizing something, such as a plan, design, or requirement.
-
C.
implementedThrough
Indicates that something is realized, carried out, or made operational by means of a specified method, mechanism, or intermediary.
-
D.
usesStrategy
chosen
Indicates that an entity intentionally applies a particular strategy or method to achieve a goal or perform an action.
-
E.
implementationForm
Indicates the specific manner, format, or method by which something is implemented or realized in practice.
- 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_69a88b074b908190ae983dbca7757d88 |
completed | March 4, 2026, 7:41 p.m. |
| NER | Named-entity recognition | batch_69abc685f05481909c863b29d1f6bacd |
completed | March 7, 2026, 6:32 a.m. |
| PD | Predicate disambiguation | batch_69abc58e88e481908733fdf79d3f8a15 |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:49 p.m.