Triple
T9278024
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Military Service Act of 1917 |
E222998
|
entity |
| Predicate | requiredService |
P34130
|
FINISHED |
| Object | overseas military service |
—
|
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: overseas military service | Statement: [Military Service Act of 1917, requiredService, overseas military service]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiredService Context triple: [Military Service Act of 1917, requiredService, overseas military service]
-
A.
serviceUserRequirement
Indicates that a user has a specific requirement or need that a service is expected to fulfill.
-
B.
requiredToProvide
Indicates that one entity has an obligation or duty to supply or furnish something to another entity.
-
C.
requiredBy
Indicates that one entity depends on or cannot function properly without another entity being present, completed, or satisfied.
-
D.
requires
Indicates that one entity must exist, occur, or be satisfied before another entity can exist, occur, or be carried out.
-
E.
typicalServiceRequirement
chosen
Indicates that a certain condition, resource, or specification is normally needed or expected for a service to be properly provided or operated.
- 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_69ca842123588190b3f2e1a69037d141 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd07cb28e081909b2754756c8f5dd0 |
completed | April 1, 2026, 11:55 a.m. |
| PD | Predicate disambiguation | batch_69cc7a576ec88190bbb787eb82e2e539 |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:34 p.m.