Triple
T22645006
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Divisor |
E558934
|
entity |
| Predicate | intendedAudienceRole |
P72617
|
FINISHED |
| Object | active participant |
—
|
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: active participant | Statement: [Divisor, intendedAudienceRole, active participant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intendedAudienceRole Context triple: [Divisor, intendedAudienceRole, active participant]
-
A.
audienceRole
chosen
Indicates the role or function an entity has as part of an audience in relation to another entity or event.
-
B.
designedRole
Indicates that one entity has been created, configured, or intended to serve a particular function, purpose, or role in relation to another entity.
-
C.
roleOfPeopleOnIt
Indicates the specific roles or functions that people have in relation to a particular object, event, or context.
-
D.
roleAccordingTo
Indicates that an entity holds a particular role or function as defined or interpreted by a specified source or perspective.
-
E.
roleInName
Indicates that a specific role, title, or position is included as part of an entity’s name or naming expression.
- 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_69e24547f7fc819086e2c4ba3b979657 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f170371fe08190a6a53809d185f8b5 |
completed | April 29, 2026, 2:43 a.m. |
| PD | Predicate disambiguation | batch_69ee6294c4c08190b7e4829f4b9af24b |
completed | April 26, 2026, 7:08 p.m. |
Created at: April 17, 2026, 3:05 p.m.