Triple
T28354045
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Remington Arms (contract) |
E718175
|
entity |
| Predicate | contractorRole |
P50446
|
FINISHED |
| Object | arms manufacturer |
—
|
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: arms manufacturer | Statement: [Remington Arms (contract), contractorRole, arms manufacturer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: contractorRole Context triple: [Remington Arms (contract), contractorRole, arms manufacturer]
-
A.
typeOfContractor
chosen
Indicates the specific category or role of a contractor in relation to a given entity or project.
-
B.
notableContractor
Indicates that one entity serves as a contractor for another in a way that is distinguished, prominent, or otherwise noteworthy.
-
C.
primaryContractor
Indicates that one entity serves as the main responsible contractor for a project, agreement, or work in relation to another entity.
-
D.
launchContractor
Indicates that one entity serves as the contractor responsible for carrying out or managing the launch of another entity.
-
E.
architecturalRole
Indicates the functional or design-related role that one entity plays within the structure, layout, or organization of another entity.
- 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_69eff6ec27b481908c8d7b86c47893d9 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f7a225a77c81908f8953ccfeb14336 |
completed | May 3, 2026, 7:29 p.m. |
| PD | Predicate disambiguation | batch_69f7a06d4f108190bae3ab9ae431d2c7 |
completed | May 3, 2026, 7:22 p.m. |
Created at: April 28, 2026, 12:48 a.m.