Triple
T33393883
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. Army firearms |
E855119
|
entity |
| Predicate | maintenancePerformedBy |
P182775
|
FINISHED |
| Object | U.S. Army armorers |
—
|
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: U.S. Army armorers | Statement: [U.S. Army firearms, maintenancePerformedBy, U.S. Army armorers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maintenancePerformedBy Context triple: [U.S. Army firearms, maintenancePerformedBy, U.S. Army armorers]
-
A.
maintenanceOrganization
chosen
Indicates the organization responsible for performing or overseeing maintenance activities on the associated entity.
-
B.
maintenanceType
Indicates the specific category or kind of maintenance activity associated with an entity or relationship.
-
C.
maintenanceAuthority
Indicates that one entity has the responsibility or official power to maintain, service, or keep another entity in proper working condition.
-
D.
hasMaintenanceService
Indicates that an entity receives or is covered by a maintenance service provided by another entity.
-
E.
hasMaintenance
Indicates that an entity is subject to, associated with, or requires a particular maintenance activity or maintenance record.
- 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_69f3496e3f1c8190bcecfa82aa9d17ff |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7c29e1b848190b945c6c6120a5330 |
completed | May 3, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69f7c1b6e7a881908deb96bedb2713f4 |
completed | May 3, 2026, 9:44 p.m. |
Created at: May 1, 2026, 1:35 a.m.