Triple
T18564664
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 3986 |
E453731
|
entity |
| Predicate | definesABNF |
P38052
|
FINISHED |
| Object | URI syntax grammar |
—
|
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: URI syntax grammar | Statement: [RFC 3986, definesABNF, URI syntax grammar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definesABNF Context triple: [RFC 3986, definesABNF, URI syntax grammar]
-
A.
definesSyntax
chosen
Indicates that one entity specifies or determines the formal structure, rules, or grammar by which another entity is expressed or interpreted.
-
B.
declarationRule
Indicates that a specific rule or guideline governs how a declaration (such as a statement, definition, or announcement) must be formed, structured, or interpreted in relation to other elements.
-
C.
eraDefinition
Indicates the specific time period or historical era during which something is defined, classified, or considered valid.
-
D.
definesLineTerminator
Indicates that one entity specifies what character or sequence of characters marks the end of a line for another entity.
-
E.
notationType
Indicates the specific system or style of notation used to represent or encode something (such as music, math, or language).
- 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_69d8d38974308190a9174430ef256b73 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e53afd8114819093b57d86f8213311 |
completed | April 19, 2026, 8:28 p.m. |
| PD | Predicate disambiguation | batch_69e478c16e0c8190b03966aa23c395a6 |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:42 a.m.