Triple
T25186644
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Enterprise NX-01 |
E630735
|
entity |
| Predicate | armoryOfficer |
P143523
|
FINISHED |
| Object | Malcolm Reed |
—
|
NE NERFINISHED |
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: Malcolm Reed | Statement: [Enterprise NX-01, armoryOfficer, Malcolm Reed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: armoryOfficer Context triple: [Enterprise NX-01, armoryOfficer, Malcolm Reed]
-
A.
armory
Indicates that an entity serves as a place where weapons, armor, or military equipment are stored, maintained, or supplied for use.
-
B.
hasSergeantAtArms
Indicates that an organization, body, or group is associated with and formally appoints a specific individual to serve in the role of Sergeant-at-Arms.
-
C.
isMilitaryStaffOf
chosen
Indicates that one entity serves as military personnel working for, or assigned to, another entity (such as an organization, unit, or individual).
-
D.
armedBy
Indicates that one entity is supplied with weapons, equipment, or armaments by another entity.
-
E.
armamentStores
Indicates that one entity stores, houses, or contains armaments or weapons for another entity or for a particular purpose.
- 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_69e75a8a6d088190ba1e82a4345225e7 |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f46e0aeb588190b3ee13a6c031c223 |
completed | May 1, 2026, 9:10 a.m. |
| PD | Predicate disambiguation | batch_69f44d8043b081908bbffd7f044b4f26 |
completed | May 1, 2026, 6:51 a.m. |
Created at: April 21, 2026, 12:44 p.m.