Triple
T34568489
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ritter |
E887556
|
entity |
| Predicate | typicalBasisForGrant |
P140646
|
FINISHED |
| Object | 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: military service | Statement: [Ritter, typicalBasisForGrant, military service]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalBasisForGrant Context triple: [Ritter, typicalBasisForGrant, military service]
-
A.
grantedOnBasisOf
Indicates that something (such as a right, status, or benefit) is conferred or awarded because of a specified reason, criterion, or underlying justification.
-
B.
typicalAwardBasis
chosen
Indicates the usual criterion or grounds on which an award is granted or decided.
-
C.
isTypicallyGrantedTo
Indicates that something is customarily or usually given, awarded, or allowed to a particular recipient or group.
-
D.
conferralBasis
Indicates the underlying reason, criterion, or justification on which something (such as a status, right, or benefit) is granted or conferred.
-
E.
grantedBy
Indicates that a right, permission, or benefit is conferred or authorized by one entity to another.
- 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_69f349d1a5fc81908557a46875b2f157 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379fd7aac8190873077e63873aa72 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 2:02 a.m.