Triple
T35815480
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IFIP Working Group 2.10 |
E1035347
|
entity |
| Predicate | parentCommitteeField |
P196160
|
FINISHED |
| Object | software: theory and practice |
—
|
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: software: theory and practice | Statement: [IFIP Working Group 2.10, parentCommitteeField, software: theory and practice]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parentCommitteeField Context triple: [IFIP Working Group 2.10, parentCommitteeField, software: theory and practice]
-
A.
parentCommittee
Indicates that one committee serves as the higher-level or overseeing committee for another committee.
-
B.
hasSiblingCommittee
Indicates that one committee is recognized as a sibling committee of another, typically meaning they are parallel or equivalent bodies within the same organizational structure.
-
C.
hasCommittee
Indicates that an entity is associated with or overseen by a specific committee.
-
D.
supportsCommittee
Indicates that one entity provides backing, endorsement, or assistance to a committee.
-
E.
hasCommitteeType
Indicates that an entity is associated with a committee of a specified type or classification.
- 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_69f76e1762408190b885a8456862e372 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fe0d165a48819098b854318a50d76c |
completed | May 8, 2026, 4:19 p.m. |
| PD | Predicate disambiguation | batch_69fe0931002481908a95b34f95e9f64e |
completed | May 8, 2026, 4:02 p.m. |
| PDg | Predicate description generation | batch_69fe0d14778c8190986fa4f37f992a2f |
completed | May 8, 2026, 4:19 p.m. |
Created at: May 3, 2026, 4:06 p.m.