Triple
T29547663
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 1327 |
E749672
|
entity |
| Predicate | hasTransportProtocol |
P10376
|
FINISHED |
| Object | SMTP |
—
|
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: SMTP | Statement: [RFC 1327, hasTransportProtocol, SMTP]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTransportProtocol Context triple: [RFC 1327, hasTransportProtocol, SMTP]
-
A.
hasProtocol
Indicates that an entity uses, follows, or is governed by a specified protocol or set of procedural rules.
-
B.
hasTransportFunction
Indicates that an entity serves to move or carry something (such as people, goods, or signals) from one place or state to another.
-
C.
hasTransportContext
Indicates that there exists a transportation-related situation, setting, or conditions under which the associated entities or actions take place.
-
D.
transportProtocol
chosen
Indicates the communication protocol used to transport data between entities in a networked interaction.
-
E.
hasApproximateTransport
Indicates that one entity is connected to another by a transport option whose route, timing, or characteristics are similar to, but not exactly the same as, a referenced or ideal transport connection.
- 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_69f0bd48691081908cecad39bac591e0 |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69fde49a084081909d99b1e0258169d5 |
completed | May 8, 2026, 1:26 p.m. |
| PD | Predicate disambiguation | batch_69fde1d04bd881909a46ecbbf18dfe59 |
completed | May 8, 2026, 1:14 p.m. |
Created at: April 28, 2026, 5:09 p.m.