Triple
T230596
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ACM Distinguished Member |
E4401
|
entity |
| Predicate | isTitleHeldBy |
P1911
|
FINISHED |
| Object | individual persons |
—
|
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: individual persons | Statement: [ACM Distinguished Member, isTitleHeldBy, individual persons]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isTitleHeldBy Context triple: [ACM Distinguished Member, isTitleHeldBy, individual persons]
-
A.
hasTitleHolder
chosen
Indicates that one entity is the current or designated holder of a specific title, position, or honor associated with another entity.
-
B.
titleHeldIn
Indicates that a particular title or position is held within a specified organization, jurisdiction, or contextual domain.
-
C.
isUsuallyHeldBy
Indicates that something is most commonly or typically possessed, carried, or controlled by a particular entity.
-
D.
titleHolderSince
Indicates the entity that has held a particular title or position continuously from a specified starting time.
-
E.
hasRepresentativeTitle
Indicates that an entity holds a formal title or designation that serves as its primary or most commonly used label or name.
- 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_69a257363ffc81909757bde7ab3404da |
completed | Feb. 28, 2026, 2:47 a.m. |
| NER | Named-entity recognition | batch_69a25e0868708190ad551ca06cc57f4a |
completed | Feb. 28, 2026, 3:16 a.m. |
| PD | Predicate disambiguation | batch_69a25b5a075081909b0e9b88c1492d5a |
completed | Feb. 28, 2026, 3:04 a.m. |
Created at: Feb. 28, 2026, 2:53 a.m.