Triple
T6501116
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Army ROTC |
E148889
|
entity |
| Predicate | commissioningComponent |
P71238
|
FINISHED |
| Object | Active Duty |
—
|
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: Active Duty | Statement: [Army ROTC, commissioningComponent, Active Duty]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commissioningComponent Context triple: [Army ROTC, commissioningComponent, Active Duty]
-
A.
plannedComponent
Indicates that one entity is intended or scheduled to serve as a component or part of another entity in a planned or future configuration.
-
B.
commissioningSource
Indicates the origin or authority (such as an institution, program, or body) that formally granted someone their commission or official appointment.
-
C.
component1
Indicates that one entity functions as a constituent or part of another entity within a larger whole.
-
D.
component3
Indicates that one entity is the third component or sub-part within a larger composite structure or system involving another entity.
-
E.
componentAct
Indicates that an action or behavior is performed by a component as part of a larger system or process.
- F. None of above. chosen
Provenance (4 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_69c687e9ad288190bae5bcac9c8ac855 |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c69f386aa08190bfc8592a92ec6339 |
completed | March 27, 2026, 3:16 p.m. |
| PD | Predicate disambiguation | batch_69c68ab714908190aa7c2fbf64078e15 |
completed | March 27, 2026, 1:48 p.m. |
| PDg | Predicate description generation | batch_69c69f362ee4819090e8fa48caef7d7d |
completed | March 27, 2026, 3:16 p.m. |
Created at: March 27, 2026, 1:42 p.m.