Triple
T28209769
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States Marine Corps general |
E711125
|
entity |
| Predicate | typicalBilletLength |
P18065
|
FINISHED |
| Object | 2 to 4 years |
—
|
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: 2 to 4 years | Statement: [United States Marine Corps general, typicalBilletLength, 2 to 4 years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalBilletLength Context triple: [United States Marine Corps general, typicalBilletLength, 2 to 4 years]
-
A.
typicalBillet
Indicates that something serves as a standard or characteristic billet or assignment for a given role, context, or entity.
-
B.
typicalLength
chosen
Indicates the usual or characteristic length associated with an entity or phenomenon.
-
C.
billLength
Indicates the length measurement of a bill or beak as a characteristic of an entity.
-
D.
typicalBilletsInclude
Indicates that certain items or roles are commonly or normally included within a given set of billets.
-
E.
inningLength
Indicates the duration or number of units (e.g., outs, minutes, or pitches) that make up a single inning in a game or sporting event.
- 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_69efb51cb5288190818c1f63a266af11 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_6a0076c0a5c4819088b17b95511b93ed |
completed | May 10, 2026, 12:14 p.m. |
| PD | Predicate disambiguation | batch_6a007638a67c81909c091335142260ab |
completed | May 10, 2026, 12:12 p.m. |
Created at: April 27, 2026, 10:38 p.m.