Triple
T26813374
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ACM Fellows Award |
E672057
|
entity |
| Predicate | honorificPrefixGranted |
P536
|
FINISHED |
| Object | ACM Fellow |
—
|
NE NERFINISHED |
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: ACM Fellow | Statement: [ACM Fellows Award, honorificPrefixGranted, ACM Fellow]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: honorificPrefixGranted Context triple: [ACM Fellows Award, honorificPrefixGranted, ACM Fellow]
-
A.
honorificPrefix
chosen
Indicates the formal title or respectful prefix (e.g., "Dr.", "Mr.", "Prof.") used before a person's name to denote status, role, or honor.
-
B.
confersHonorificStatus
Indicates that one entity formally grants an honorific title, rank, or status to another entity.
-
C.
honoraryPrefix
Indicates that one entity serves as an honorific title or respectful prefix attached to the name of another entity.
-
D.
hasHonorificStatus
Indicates that an entity holds or is assigned a particular honorific title, rank, or status in relation to another entity.
-
E.
hasHonorificPrefix
Indicates that one entity is used as an honorific title or prefix attached to another entity’s 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_69eeb3225a3c8190aaf6746efeded2f3 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f6640168948190811bd5f933a87cf5 |
completed | May 2, 2026, 8:52 p.m. |
| PD | Predicate disambiguation | batch_69f6633451948190bcc0410602bb4914 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 27, 2026, 4:30 a.m.