Triple
T3425433
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PLDI |
E72217
|
entity |
| Predicate | hasTopicCategory |
P15481
|
FINISHED |
| Object | theory and practice of programming languages |
—
|
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: theory and practice of programming languages | Statement: [PLDI, hasTopicCategory, theory and practice of programming languages]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTopicCategory Context triple: [PLDI, hasTopicCategory, theory and practice of programming languages]
-
A.
hasCategoryOn
chosen
Indicates that something is assigned to or associated with a specific category within a given context or scope.
-
B.
hasCategoryWithin
Indicates that one category is contained within or is a subcategory of another category.
-
C.
hasCategoryGroup
Indicates that something is associated with, or belongs to, a broader grouping of related categories.
-
D.
hasCategoryLevel
Indicates that something is associated with a specific hierarchical category or tier within a classification system.
-
E.
hasRelatedCategory
Indicates that one category is associated with another category through a non-hierarchical, contextually relevant relationship.
- 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_69ad85ae14308190bcbc25cfa0246c0b |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb97fa2d88190a79cb8c7be4b3696 |
completed | March 8, 2026, 6:01 p.m. |
| PD | Predicate disambiguation | batch_69adadfea024819094b41a13bc004bda |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:15 p.m.