Triple
T270931
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HTTP/3 |
E5630
|
entity |
| Predicate | relatedRFC |
P9936
|
FINISHED |
| Object | RFC 9110 |
—
|
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: RFC 9110 | Statement: [HTTP/3, relatedRFC, RFC 9110]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedRFC Context triple: [HTTP/3, relatedRFC, RFC 9110]
-
A.
relatedField
Indicates that one field, topic, or area of study is connected or relevant to another in subject matter or application.
-
B.
relatedTo
Indicates a general, non-specific relationship or association exists between two entities.
-
C.
relatedCase
Indicates that one legal case is connected or associated with another case, such as through shared facts, parties, issues, or procedural history.
-
D.
relatedCode
Indicates that one code is associated with, linked to, or otherwise contextually connected to another code.
-
E.
relatedToTreaty
Indicates that there exists a connection, association, or relevance between an entity and a specific treaty or treaties.
- 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_69a25853594c8190b05ec3a586ec88bf |
completed | Feb. 28, 2026, 2:52 a.m. |
| NER | Named-entity recognition | batch_69a25e69a9248190b9e7959b43223baa |
completed | Feb. 28, 2026, 3:18 a.m. |
| PD | Predicate disambiguation | batch_69a25b721180819080d43c43fcbccf87 |
completed | Feb. 28, 2026, 3:05 a.m. |
| PDg | Predicate description generation | batch_69a25e68f0408190bfc851c32d6eebf3 |
completed | Feb. 28, 2026, 3:18 a.m. |
Created at: Feb. 28, 2026, 2:57 a.m.