Triple
T32333359
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 2253 |
E826107
|
entity |
| Predicate | relatesToVersion |
P75898
|
FINISHED |
| Object | LDAPv3 |
E827891
|
NE 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: LDAPv3 | Statement: [RFC 2253, relatesToVersion, LDAPv3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatesToVersion Context triple: [RFC 2253, relatesToVersion, LDAPv3]
-
A.
isVersionOf
Indicates that one entity is a particular version, edition, or variant derived from another entity.
-
B.
relatedToProtocolVersion
chosen
Indicates a relationship where something is associated with, governed by, or dependent on a specific protocol version.
-
C.
relatesToBranch
Indicates a general association or connection between an entity and a specific branch (such as a subdivision, offshoot, or subunit) within a larger structure or system.
-
D.
basedOnVersion
Indicates that one entity is derived from, built upon, or created using a specific version of another entity as its basis.
-
E.
isTemporaryVersionOf
Indicates that one entity is a non-final, short-lived or provisional form of another, more permanent entity.
- F. None of above.
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_69f34913d9048190befaa634025232be |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3057267b188190abe68b242839fbe6 |
completed | June 15, 2026, 7:48 p.m. |
| PD | Predicate disambiguation | batch_6a0379edf2d88190b492fca86ed23cac |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 12:47 a.m.