Triple
T22710195
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ECL |
E561571
|
entity |
| Predicate | canCompileTo |
P29008
|
FINISHED |
| Object | C |
—
|
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: C | Statement: [ECL, canCompileTo, C]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canCompileTo Context triple: [ECL, canCompileTo, C]
-
A.
compiledTo
chosen
Indicates that one artifact (such as source code) has been transformed into another, typically lower-level or executable form, through a compilation process.
-
B.
laterCompiledAs
Indicates that one work, version, or material was subsequently gathered, edited, or assembled into another compiled work.
-
C.
compilationType
Indicates the specific method or mode by which something is compiled or assembled into a final form.
-
D.
compiledIn
Indicates that a piece of code, program, or module was compiled within or for a specific environment, system, or context.
-
E.
supportsStreamingCompilation
Indicates that an entity is capable of performing compilation in a streaming manner, processing and compiling input incrementally as it is received rather than requiring the entire input up front.
- 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_69e2454f1348819088d83f420925a5c1 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f178d1e24881909ebd4531c0daef7f |
completed | April 29, 2026, 3:19 a.m. |
| PD | Predicate disambiguation | batch_69ee62bd657c81909f7b01245b080a5f |
completed | April 26, 2026, 7:08 p.m. |
Created at: April 17, 2026, 3:17 p.m.