Triple
T22239698
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | General Standard |
E549686
|
entity |
| Predicate | requiresEnglishReporting |
P103498
|
FINISHED |
| Object | no general obligation, unlike Prime Standard |
—
|
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: no general obligation, unlike Prime Standard | Statement: [General Standard, requiresEnglishReporting, no general obligation, unlike Prime Standard]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresEnglishReporting Context triple: [General Standard, requiresEnglishReporting, no general obligation, unlike Prime Standard]
-
A.
requiresReportTo
Indicates that one entity is obligated to submit or provide a report to another entity.
-
B.
requiredLanguage
chosen
Indicates that a specific language is necessary or must be used for a given entity, action, or interaction.
-
C.
languageOfOfficialReports
Indicates the language in which an entity’s official reports are written or issued.
-
D.
requiresReportFrom
Indicates that one entity is obligated to obtain or receive a report from another entity.
-
E.
requiredReportOn
Indicates that one entity is obligated to produce or submit a report concerning another entity or subject.
- 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_69e11e4102b881909cf47d3768e25c19 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f132133b908190b0fb32a5ee68e1e6 |
completed | April 28, 2026, 10:17 p.m. |
| PD | Predicate disambiguation | batch_69e71b5177d881908f90abde14ada7dc |
completed | April 21, 2026, 6:38 a.m. |
Created at: April 16, 2026, 8:38 p.m.