Triple
T66257
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SecDef |
E1320
|
entity |
| Predicate | prohibitsActiveDutyHolder |
P272
|
FINISHED |
| Object | except by congressional waiver |
—
|
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: except by congressional waiver | Statement: [SecDef, prohibitsActiveDutyHolder, except by congressional waiver]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: prohibitsActiveDutyHolder Context triple: [SecDef, prohibitsActiveDutyHolder, except by congressional waiver]
-
A.
prohibits
chosen
Indicates that one entity forbids or disallows another entity from performing a specific action or being in a certain state.
-
B.
officeHoldersMustBe
Indicates that individuals who hold a particular office are required to possess a specified status, qualification, or characteristic.
-
C.
notCommanderOf
Indicates that a given entity does not hold a commanding or leadership role over another specified entity.
-
D.
hasMilitaryBranch
Indicates that an entity is associated with, served in, or is part of a specific branch of a military organization.
-
E.
positionHeld
Indicates that an entity occupies or has occupied a specific role, job, office, or position within an organization or context.
- 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_69a24ba4f760819081f6638a3c70538a |
completed | Feb. 28, 2026, 1:57 a.m. |
| NER | Named-entity recognition | batch_69a2516eda54819090f5c14384d4eab1 |
completed | Feb. 28, 2026, 2:22 a.m. |
| PD | Predicate disambiguation | batch_69a24ea5c140819080409a968c8d2ce8 |
completed | Feb. 28, 2026, 2:10 a.m. |
Created at: Feb. 28, 2026, 2:02 a.m.