Triple
T30053296
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Defense Service Offices |
E763658
|
entity |
| Predicate | typicalProceedings |
—
|
GENERATED |
| Object | special courts-martial |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalProceedings Context triple: [Defense Service Offices, typicalProceedings, special courts-martial]
-
A.
typeOfProceedings
chosen
Indicates the specific category or kind of legal or formal process under which an action or case is being conducted.
-
B.
recordsProceedings
Indicates that an entity documents or captures the details of proceedings, such as events, meetings, or legal actions.
-
C.
proceedingsAre
Indicates that certain events, actions, or legal steps constitute or are recognized as formal proceedings.
-
D.
scriptUsedForProceedings
Indicates that a particular writing system or script is used to record, document, or conduct the referenced proceedings.
-
E.
coversProceedings
Indicates that one entity reports on, documents, or provides coverage of a set of proceedings or events involving another entity.
- F. None of above.
Provenance (1 batch)
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_69f224716378819087a722e487832b70 |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 6:56 p.m.