Triple
T574801
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SIGCAS |
E13738
|
entity |
| Predicate | hasSubcommunity |
P2605
|
FINISHED |
| Object | academics interested in computers and society |
—
|
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: academics interested in computers and society | Statement: [SIGCAS, hasSubcommunity, academics interested in computers and society]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSubcommunity Context triple: [SIGCAS, hasSubcommunity, academics interested in computers and society]
-
A.
hasSubcommunityIn
chosen
Indicates that a larger community contains or encompasses a smaller, distinct subcommunity located within it.
-
B.
hasCommunityType
Indicates that an entity is associated with or classified under a particular type or category of community.
-
C.
hasCommunitySpace
Indicates that an entity provides or includes a shared physical or virtual area intended for communal use, activities, or gatherings.
-
D.
hasNearbyCommunity
Indicates that one entity has another community located close to it in geographic or spatial terms.
-
E.
hasSubdivision
Indicates that one entity is divided into and contains another entity as one of its constituent parts or administrative units.
- 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_69a4933fa4d88190a7949cc83c08c5c1 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49b4c23548190a3b883239c7c78c8 |
completed | March 1, 2026, 8:02 p.m. |
| PD | Predicate disambiguation | batch_69a494c4969c819080375d08f9eec50c |
completed | March 1, 2026, 7:34 p.m. |
Created at: March 1, 2026, 7:33 p.m.