Triple
T27582493
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 4918 |
E699617
|
entity |
| Predicate | definesExtensionOf |
P83929
|
FINISHED |
| Object | HTTP |
—
|
NE NERFINISHED |
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: HTTP | Statement: [RFC 4918, definesExtensionOf, HTTP]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definesExtensionOf Context triple: [RFC 4918, definesExtensionOf, HTTP]
-
A.
definesExtension
chosen
Indicates that one entity specifies or establishes the extension, scope, or detailed form of another entity.
-
B.
usesExtensionOf
Indicates that one entity makes use of another entity that is an extension or extended version of something else.
-
C.
isOnExtensionOf
Indicates that one entity lies along or continues the straight-line extension of another entity beyond its endpoint.
-
D.
extendsTo
Indicates that one entity reaches, stretches, or continues its scope, influence, or coverage up to or into another entity.
-
E.
fieldExtensionOf
Indicates that one field is an extension of another, meaning it contains the smaller field as a subfield and enlarges it by adding new elements while preserving field operations.
- 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_69ef6a4cb8b881909b3a8d630fd89df2 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f71422adac8190a5ceb32dcf820833 |
completed | May 3, 2026, 9:23 a.m. |
| PD | Predicate disambiguation | batch_69f712764d2c819081b64b27e5de4a13 |
completed | May 3, 2026, 9:16 a.m. |
Created at: April 27, 2026, 2:03 p.m.