Triple
T28354041
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Remington Arms (contract) |
E718175
|
entity |
| Predicate | signingPeriod |
P4326
|
FINISHED |
| Object | 1914 |
—
|
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: 1914 | Statement: [Remington Arms (contract), signingPeriod, 1914]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: signingPeriod Context triple: [Remington Arms (contract), signingPeriod, 1914]
-
A.
registrationPeriod
Indicates the time span during which registration for something is open or valid.
-
B.
signedDuring
chosen
Indicates that an agreement, document, or contract was signed within a specified time period or during a particular event.
-
C.
significantCollectionPeriod
Indicates that the time span over which something is gathered, measured, or accumulated is long or substantial enough to be considered important or impactful.
-
D.
establishedPeriod
Indicates the time span or date range during which something was founded, created, or formally brought into existence.
-
E.
qualificationPeriod
Indicates the time span during which a party or entity must meet specified conditions or criteria to be considered qualified.
- 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_69f6c1265c208190aacd2b551f8f0f82 |
completed | May 3, 2026, 3:29 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2415fc81908c23c311aebce66f |
completed | May 3, 2026, 3:12 a.m. |
Created at: April 28, 2026, 12:48 a.m.