Triple
T29547630
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 1327 |
E749672
|
entity |
| Predicate | definesMappingBetween |
P8534
|
FINISHED |
| Object | X.400 electronic mail |
—
|
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 electronic mail | Statement: [RFC 1327, definesMappingBetween, X.400 electronic mail]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definesMappingBetween Context triple: [RFC 1327, definesMappingBetween, X.400 electronic mail]
-
A.
definesRelationshipBetween
chosen
Indicates that one entity specifies or establishes the nature, type, or rules of a relationship that exists between two or more other entities.
-
B.
typicalMapping
Indicates a standard or commonly used correspondence between elements of one set, structure, or representation and those of another.
-
C.
mappingBy
Indicates that one entity is related to another through a defined mapping or association, specifying which side or field governs the relationship.
-
D.
mappedUsing
Indicates that one entity is associated or transformed into another entity through a specified mapping method or mechanism.
-
E.
mapsTo
Indicates that one entity is associated with or transformed into another entity, typically defining a directional correspondence or function from a source to a target.
- 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_69fcf36d2894819089b7db8e91b63c9d |
completed | May 7, 2026, 8:17 p.m. |
| PD | Predicate disambiguation | batch_69fcf25c0a108190bfa823474098640b |
completed | May 7, 2026, 8:13 p.m. |
Created at: April 28, 2026, 5:09 p.m.