Triple
T8601192
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 1907 |
E203677
|
entity |
| Predicate | definesObjectType |
P56536
|
FINISHED |
| Object | sysDescr |
—
|
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: sysDescr | Statement: [RFC 1907, definesObjectType, sysDescr]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definesObjectType Context triple: [RFC 1907, definesObjectType, sysDescr]
-
A.
definesType
chosen
Indicates that one entity specifies or establishes the type or classification of another entity.
-
B.
definesMessageType
Indicates that one entity specifies or determines the message type classification or category for another entity.
-
C.
typicalObjectType
Indicates that something is a common or characteristic type of object typically associated with or involved in another entity or situation.
-
D.
definitionType
Indicates the specific kind or category of definition that characterizes how one entity is defined in relation to another.
-
E.
definesProfileType
Indicates that an entity specifies or assigns the particular profile type associated with another entity.
- 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_69ca832b56948190ba751cec255308f1 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cc46d8ff408190acc7cd8dc99b2689 |
completed | March 31, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69cc454eb2908190acf0e4336bc67e7b |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:24 p.m.