Triple
T12300283
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | flag of Russia |
E293200
|
entity |
| Predicate | firstUseAsMerchantFlag |
P1929
|
FINISHED |
| Object | late 17th century |
—
|
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: late 17th century | Statement: [flag of Russia, firstUseAsMerchantFlag, late 17th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstUseAsMerchantFlag Context triple: [flag of Russia, firstUseAsMerchantFlag, late 17th century]
-
A.
firstUsedFor
Indicates that one entity was the earliest or original thing for which another entity was used or applied.
-
B.
usedToAuthorize
Indicates that something serves as the basis or instrument for granting permission, approval, or official power to perform an action.
-
C.
firstUsedAt
Indicates the time or place at which something was initially used or put into operation.
-
D.
firstCommercialUse
chosen
Indicates the earliest point in time at which something was used commercially or put into commercial operation.
-
E.
firstToAuthorize
Indicates that one entity is the earliest or initial party to grant approval, permission, or authorization for a particular action or arrangement relative to others.
- 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_69d6ab6a2b50819082f6aedd32ed608a |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d93f621570819091ee1db2609233ea |
completed | April 10, 2026, 6:20 p.m. |
| PD | Predicate disambiguation | batch_69d93ec02c008190a56aae60a3d9eff6 |
completed | April 10, 2026, 6:17 p.m. |
Created at: April 8, 2026, 9:53 p.m.