Triple
T1776197
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Flag of New Jersey |
E38984
|
entity |
| Predicate | designStandardized |
P7508
|
FINISHED |
| Object | 1896-03-26 |
—
|
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: 1896-03-26 | Statement: [Flag of New Jersey, designStandardized, 1896-03-26]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designStandardized Context triple: [Flag of New Jersey, designStandardized, 1896-03-26]
-
A.
documentationStandard
Indicates that there is a specified convention or set of rules governing how documentation should be written, structured, or maintained in relation to an entity or process.
-
B.
standardizedIn
chosen
Indicates that something has been formally defined, regulated, or made uniform within a particular standard, framework, or jurisdiction.
-
C.
codeStandard
Indicates that an entity adheres to, complies with, or is governed by a specified coding or programming standard.
-
D.
standardizedBy
Indicates that one entity defines, regulates, or formalizes the standards or specifications by which another entity is created, measured, or operated.
-
E.
standardizationApproach
Indicates the method or strategy used to establish, implement, or align with a common standard across entities or processes.
- 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_69a8862e61708190af97b9838cc3f5de |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69ab74dc9d1481908084ef07872a71f8 |
completed | March 7, 2026, 12:44 a.m. |
| PD | Predicate disambiguation | batch_69aa61cf3ca881908641fd73ce2f7c9d |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:31 p.m.