Triple
T29547640
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 1327 |
E749672
|
entity |
| Predicate | concernsStandard |
P178054
|
FINISHED |
| Object | X.400(1988) |
—
|
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: X.400(1988) | Statement: [RFC 1327, concernsStandard, X.400(1988)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: concernsStandard Context triple: [RFC 1327, concernsStandard, X.400(1988)]
-
A.
concernsClause
Indicates that one entity (such as a document, statement, or discussion) is about, relates to, or addresses a particular clause.
-
B.
concernsText
Indicates that something is about or relates specifically to a given piece of text.
-
C.
concernsAddressed
Indicates that specific issues, worries, or topics raised by one party have been acknowledged and dealt with by another party.
-
D.
concernsProvision
Indicates a relationship where something is about, deals with, or relates to the supplying or making available of resources, services, or necessities.
-
E.
concernsStage
Indicates that something is related or pertains specifically to a particular stage or phase within a process, lifecycle, or sequence.
- 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_69f0bd48691081908cecad39bac591e0 |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69f707f7959881908f037f0d6b1d0c36 |
completed | May 3, 2026, 8:31 a.m. |
| PD | Predicate disambiguation | batch_69f700fc274c8190a128593dc7c7abd0 |
completed | May 3, 2026, 8:02 a.m. |
| PDg | Predicate description generation | batch_69f707f380388190954b79d52a321921 |
completed | May 3, 2026, 8:31 a.m. |
Created at: April 28, 2026, 5:09 p.m.