Triple
T29607032
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GraphQL.js |
E754602
|
entity |
| Predicate | intendedRuntime |
P66719
|
FINISHED |
| Object | Node.js |
—
|
NE NERFINISHED |
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: Node.js | Statement: [GraphQL.js, intendedRuntime, Node.js]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intendedRuntime Context triple: [GraphQL.js, intendedRuntime, Node.js]
-
A.
runTimeSupport
Indicates that one entity provides or requires support for another entity during its execution at run time.
-
B.
originalRuntime
Indicates the initial or primary duration associated with something, typically before any edits, changes, or adjustments are made.
-
C.
primaryRuntime
chosen
Indicates the main runtime environment or platform under which an entity (such as a program, service, or component) is intended to execute.
-
D.
intendedSystem
Indicates that one entity is the target or designated system for which another entity is designed, directed, or meant to operate.
-
E.
intendedPerformanceMode
Indicates the manner or mode in which an action, process, or performance is meant or designed to be carried out.
- 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_69f0ef84e5d08190a0df17f5930ceed3 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69f7aa699d68819081ed363931894ab3 |
completed | May 3, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69f7a8cec6d48190bebfa884b2f938c0 |
completed | May 3, 2026, 7:58 p.m. |
Created at: April 28, 2026, 6:26 p.m.