Triple
T2050916
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 783 |
E45563
|
entity |
| Predicate | definesEndOfFileCondition |
P29156
|
FINISHED |
| Object | DATA packet with less than 512 bytes |
—
|
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: DATA packet with less than 512 bytes | Statement: [RFC 783, definesEndOfFileCondition, DATA packet with less than 512 bytes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definesEndOfFileCondition Context triple: [RFC 783, definesEndOfFileCondition, DATA packet with less than 512 bytes]
-
A.
hasConditionalEnding
Indicates that one entity concludes or terminates only if a specified condition involving another entity is met.
-
B.
hasEnding
Indicates that one entity concludes with, or terminates in, another entity (such as a specific substring, segment, or final component).
-
C.
terminationCondition
chosen
Indicates the condition or set of conditions under which an ongoing process, activity, or relationship is brought to an end.
-
D.
requiresTerminatorAtEachEnd
Indicates that the related entity must have a terminator component installed or present at both of its ends.
-
E.
endsWith
Indicates that one entity terminates with, or has as its final part, the sequence or element represented by the other 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_69a8891948208190ab7898da21824c77 |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abb98f5f4881908d9aa0f10be44041 |
completed | March 7, 2026, 5:37 a.m. |
| PD | Predicate disambiguation | batch_69abb7abba508190b872f345d3ba51bb |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:39 p.m.