Triple
T8648231
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Australian Imperial Force |
E205032
|
entity |
| Predicate | volunteerForce |
P47918
|
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: [Australian Imperial Force, volunteerForce, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: volunteerForce Context triple: [Australian Imperial Force, volunteerForce, true]
-
A.
isVolunteerForce
chosen
Indicates that a group or force is composed of individuals who serve voluntarily rather than by conscription or obligation.
-
B.
volunteerOrConscript
Indicates that an entity participates in a role, service, or activity either by choosing to do so voluntarily or by being compelled or drafted into it.
-
C.
reliefForce
Indicates that one entity provides assistance or reinforcement to another entity in response to an emergency, crisis, or adverse situation.
-
D.
typeOfVolunteerUnit
Indicates that one entity is a specific kind or category of volunteer unit in relation to another entity.
-
E.
volunteeredFor
Indicates that an entity willingly offered their time or services to support or participate in an activity, cause, or organization.
- 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_69ca834e56848190abb0eeaec9dedd32 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc4812b7bc8190acb40da57cad293a |
completed | March 31, 2026, 10:17 p.m. |
| PD | Predicate disambiguation | batch_69cc45619460819091e83ffdec99c865 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:29 p.m.