Triple
T300595
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RESTCONF |
E6188
|
entity |
| Predicate | basedOn |
P98
|
FINISHED |
| Object | REST |
E1064
|
NE 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: REST | Statement: [RESTCONF, basedOn, REST]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: REST Context triple: [RESTCONF, basedOn, REST]
-
A.
RESTCONF
RESTCONF is a RESTful protocol defined by the IETF for accessing and managing configuration and operational data on network devices using YANG data models.
-
B.
HTTP
chosen
HTTP (Hypertext Transfer Protocol) is the foundational application-layer protocol used for transmitting web pages and other resources across the World Wide Web.
-
C.
RDS
RDS is a Canadian French-language sports television network that broadcasts a wide range of professional and amateur sporting events.
-
D.
RDFS
RDFS (RDF Schema) is a semantic web vocabulary language used to define the structure, classes, and properties of RDF data.
-
E.
Web 2.0
Web 2.0 refers to the second generation of the World Wide Web characterized by user-generated content, social media, interactivity, and collaboration on platforms such as blogs, wikis, and social networks.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69a2e79114b081909490b3bf5a5dbb51 |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2e9e6a8308190b9bd15310e324504 |
completed | Feb. 28, 2026, 1:13 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69a3aba14b0881908eb4f62ac9261d63 |
completed | March 1, 2026, 2:59 a.m. |
Created at: Feb. 28, 2026, 1:06 p.m.