Triple
T38525834
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Standby Reserve |
E923224
|
entity |
| Predicate | membersMayBeSubjectTo |
P1313
|
FINISHED |
| Object | recall to active duty |
—
|
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: recall to active duty | Statement: [Standby Reserve, membersMayBeSubjectTo, recall to active duty]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: membersMayBeSubjectTo Context triple: [Standby Reserve, membersMayBeSubjectTo, recall to active duty]
-
A.
isSubjectTo
chosen
Indicates that one entity is governed, affected, or constrained by the authority, rules, conditions, or influence of another entity.
-
B.
membershipCanBeInfluencedBy
Indicates that the status or outcome of a membership relationship can be affected or altered by certain factors, actions, or entities.
-
C.
eligibleMembers
Indicates that certain entities meet the required criteria or conditions to be considered eligible members of a specified group or category.
-
D.
membersAreRegardedAs
Indicates that certain individuals or entities are viewed or treated as members of a particular group or organization.
-
E.
mayHaveRestriction
Indicates that an entity can be subject to one or more limitations, conditions, or constraints, though such restrictions are not necessarily present.
- 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_69f76ea8f6348190a5c03fb6292bbee3 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fdfbafe32081909c62653ff4fc155c |
completed | May 8, 2026, 3:05 p.m. |
| PD | Predicate disambiguation | batch_69fdf64db4a881908f8250e24ae3cefb |
completed | May 8, 2026, 2:42 p.m. |
Created at: May 3, 2026, 4:32 p.m.