Triple
T3392637
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rule 201 |
E71454
|
entity |
| Predicate | standardForFacts |
P49377
|
FINISHED |
| Object | facts not subject to reasonable dispute |
—
|
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: facts not subject to reasonable dispute | Statement: [Rule 201, standardForFacts, facts not subject to reasonable dispute]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: standardForFacts Context triple: [Rule 201, standardForFacts, facts not subject to reasonable dispute]
-
A.
standardReference
Indicates that one entity serves as the authoritative or canonical reference or benchmark for interpreting, validating, or comparing another entity.
-
B.
standardType
Indicates that one entity is classified as the standard, canonical, or reference type for another entity or context.
-
C.
standardFormulation
Indicates that something is expressed or represented in a conventional, officially accepted, or commonly used form or version.
-
D.
standardizedFor
Indicates that something has been adjusted or converted to conform to a common standard, format, or reference so it can be consistently compared or used.
-
E.
standardBefore
Indicates that one standard must be satisfied, applied, or occur earlier in sequence or priority than another standard.
- F. None of above. chosen
Provenance (4 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_69ad85a9c4a88190a854019341cb3b60 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb851e57c8190983cadcedc58db50 |
completed | March 8, 2026, 5:56 p.m. |
| PD | Predicate disambiguation | batch_69adadf705608190975423779430cc58 |
completed | March 8, 2026, 5:12 p.m. |
| PDg | Predicate description generation | batch_69adb2e426b88190b82d9830149b142e |
completed | March 8, 2026, 5:33 p.m. |
Created at: March 8, 2026, 3:14 p.m.