Triple
T16747106
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SSAP |
E406984
|
entity |
| Predicate | pairedWith |
P3159
|
FINISHED |
| Object | DSAP |
E406983
|
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: DSAP | Statement: [SSAP, pairedWith, DSAP]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: DSAP Context triple: [SSAP, pairedWith, DSAP]
-
A.
DSAP
chosen
DSAP (Destination Service Access Point) is a field in IEEE 802.2 LLC headers that identifies the destination logical service or protocol endpoint within a networked device.
-
B.
DAPS
DAPS is the station code for the Domestic Airport railway station serving the domestic terminals of Sydney Airport in Australia.
-
C.
SSAP
SSAP (Source Service Access Point) is a field in IEEE 802.2 LLC headers that identifies the logical source endpoint of a network service access point for data link layer communications.
-
D.
ASDP
ASDP is the professional abbreviation for the American Society of Dermatopathology, an organization dedicated to the study and advancement of skin pathology.
-
E.
DAP
DAP (Directory Access Protocol) is an early X.500 directory service protocol that provided a complex, OSI-based method for accessing and managing directory information before being largely replaced by LDAP.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d8838ffb088190a0b11149929006bf |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3aa2311748190a17416de577ad159 |
completed | April 18, 2026, 3:58 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a00a52033748190ae207d72d437236b |
completed | May 10, 2026, 3:32 p.m. |
Created at: April 10, 2026, 5:21 a.m.