Triple
T2301886
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 23 SAS |
E51750
|
entity |
| Predicate | isVolunteerUnit |
P5502
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [23 SAS, isVolunteerUnit, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isVolunteerUnit Context triple: [23 SAS, isVolunteerUnit, true]
-
A.
hasVolunteerStatus
Indicates that an entity holds a particular volunteer-related status or role within a specified context.
-
B.
hasVolunteerBase
chosen
Indicates that an entity maintains or relies on a group of volunteers as a foundational support resource.
-
C.
hasVolunteerProgram
Indicates that an organization or entity offers an organized program through which individuals can volunteer their time or services.
-
D.
eligibilityUnit
Indicates that one entity serves as the unit or basis used to determine another entity’s eligibility for a benefit, status, or condition.
-
E.
involvedUnit
Indicates that a particular unit (such as a group, organization, or division) participates in, is associated with, or plays a role in the referenced event or activity.
- 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_69a88b0a9f248190bcff941463d8f65a |
completed | March 4, 2026, 7:42 p.m. |
| NER | Named-entity recognition | batch_69abcbabf01081908db3b42bc7c60444 |
completed | March 7, 2026, 6:54 a.m. |
| PD | Predicate disambiguation | batch_69abc58ad33c8190b8d68af41b6f5e07 |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:49 p.m.