Triple
T11655233
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Open Container Initiative |
E276997
|
entity |
| Predicate | hasWorkingGroup |
P1382
|
FINISHED |
| Object |
Runtime Working Group
The Runtime Working Group is a technical body within the Open Container Initiative responsible for defining and maintaining open industry standards for container runtime behavior and specifications.
|
E937619
|
NE FINISHED |
How this triple was built (4 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: Runtime Working Group | Statement: [Open Container Initiative, hasWorkingGroup, Runtime Working Group]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Runtime Working Group Context triple: [Open Container Initiative, hasWorkingGroup, Runtime Working Group]
-
A.
Web Applications Working Group
The Web Applications Working Group is a W3C standards body responsible for developing and maintaining core web platform APIs and specifications that enable rich, interactive web applications.
-
B.
Routing Working Group
The Routing Working Group is a RIPE community body that focuses on the development, coordination, and discussion of Internet routing policies, practices, and technologies within the RIPE region.
-
C.
W3C Working Group
A W3C Working Group is a formal body within the World Wide Web Consortium that develops and maintains web standards and related technical reports through a consensus-driven process.
-
D.
HTTP Working Group
The HTTP Working Group is an IETF standards body responsible for developing and maintaining the Hypertext Transfer Protocol and related web communication specifications.
-
E.
W3C Coordination Group
The W3C Coordination Group is a World Wide Web Consortium body responsible for overseeing and harmonizing the work of various W3C groups to ensure technical consistency and effective collaboration across web standards.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Runtime Working Group Triple: [Open Container Initiative, hasWorkingGroup, Runtime Working Group]
Generated description
The Runtime Working Group is a technical body within the Open Container Initiative responsible for defining and maintaining open industry standards for container runtime behavior and specifications.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Runtime Working Group Target entity description: The Runtime Working Group is a technical body within the Open Container Initiative responsible for defining and maintaining open industry standards for container runtime behavior and specifications.
-
A.
Web Applications Working Group
The Web Applications Working Group is a W3C standards body responsible for developing and maintaining core web platform APIs and specifications that enable rich, interactive web applications.
-
B.
Routing Working Group
The Routing Working Group is a RIPE community body that focuses on the development, coordination, and discussion of Internet routing policies, practices, and technologies within the RIPE region.
-
C.
W3C Working Group
A W3C Working Group is a formal body within the World Wide Web Consortium that develops and maintains web standards and related technical reports through a consensus-driven process.
-
D.
HTTP Working Group
The HTTP Working Group is an IETF standards body responsible for developing and maintaining the Hypertext Transfer Protocol and related web communication specifications.
-
E.
W3C Coordination Group
The W3C Coordination Group is a World Wide Web Consortium body responsible for overseeing and harmonizing the work of various W3C groups to ensure technical consistency and effective collaboration across web standards.
- F. None of above. chosen
Provenance (5 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_69d6aafbb3c081908a9cdb4ecb8d981d |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a3cee010819089cffdbefe5a6efb |
completed | April 10, 2026, 7:16 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ee88166900819095063f045be44bed |
completed | April 26, 2026, 9:48 p.m. |
| NEDg | Description generation | batch_69eeb315ebc48190a0f6ff0dc8afd462 |
completed | April 27, 2026, 12:51 a.m. |
| NED2 | Entity disambiguation (via description) | batch_69eecd954b348190bf2f3ad66acbf1b7 |
completed | April 27, 2026, 2:44 a.m. |
Created at: April 8, 2026, 9:39 p.m.