Triple
T7892954
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Naval Reserve |
E183280
|
entity |
| Predicate | volunteerStatus |
P31155
|
FINISHED |
| Object | volunteer |
—
|
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: volunteer | Statement: [Naval Reserve, volunteerStatus, volunteer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: volunteerStatus Context triple: [Naval Reserve, volunteerStatus, volunteer]
-
A.
hasVolunteerStatus
chosen
Indicates that an entity holds a particular volunteer-related status or role within a specified context.
-
B.
volunteeredFor
Indicates that an entity willingly offered their time or services to support or participate in an activity, cause, or organization.
-
C.
hasVolunteerProgram
Indicates that an organization or entity offers an organized program through which individuals can volunteer their time or services.
-
D.
typeOfVolunteerUnit
Indicates that one entity is a specific kind or category of volunteer unit in relation to another entity.
-
E.
participationStatus
Indicates the current state or condition of an entity’s involvement in an event, activity, or process (e.g., planned, active, completed, or cancelled participation).
- 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_69ca828c474c8190a254d6499871eaff |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3a008fb88190a039fec40483ab93 |
completed | March 31, 2026, 3:05 a.m. |
| PD | Predicate disambiguation | batch_69cae92b0cd881908e715a10d3252e83 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 5 p.m.