Triple
T1160037
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ECMAScript |
E24470
|
entity |
| Predicate | proposalProcess |
P25604
|
FINISHED |
| Object | multi-stage TC39 process |
—
|
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: multi-stage TC39 process | Statement: [ECMAScript, proposalProcess, multi-stage TC39 process]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: proposalProcess Context triple: [ECMAScript, proposalProcess, multi-stage TC39 process]
-
A.
proposes
Indicates that one entity formally suggests or puts forward an idea, plan, or course of action to another entity for consideration or approval.
-
B.
proposalDate
Indicates the date on which a proposal is formally made or submitted from one entity to another.
-
C.
designationProcess
Indicates the process by which an entity is formally assigned, conferred, or recognized with a particular status, role, or designation.
-
D.
proposedAmendment
Indicates that one entity has formally suggested a change or addition (an amendment) to another entity, such as a document, law, or agreement.
-
E.
advisoryProcess
Indicates a relationship where one party provides guidance, recommendations, or expert advice to another through a structured consultative process.
- F. None of above. chosen
Provenance (4 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_69a494060e148190abb42f971242c197 |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4bcaf3a9081908bad2eba74dffbc1 |
completed | March 1, 2026, 10:24 p.m. |
| PD | Predicate disambiguation | batch_69a4bb525b648190adcb7a29256d3c41 |
completed | March 1, 2026, 10:18 p.m. |
| PDg | Predicate description generation | batch_69a4bc49693c8190978ec63a5171d342 |
completed | March 1, 2026, 10:23 p.m. |
Created at: March 1, 2026, 7:45 p.m.