Triple

T29389945
Position Surface form Disambiguated ID Type / Status
Subject UFS E745346 entity
Predicate dataBus P30865 FINISHED
Object MIPI M‑PHY
MIPI M‑PHY is a high-speed, low-power physical layer interface standard developed by the MIPI Alliance for connecting mobile and embedded components such as storage, cameras, and radios.
 E1865287 NE FINISHED

How this triple was built (3 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: MIPI M‑PHY | Statement: [UFS, dataBus, MIPI M‑PHY]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: MIPI M‑PHY
Triple: [UFS, dataBus, MIPI M‑PHY]
Generated description
MIPI M‑PHY is a high-speed, low-power physical layer interface standard developed by the MIPI Alliance for connecting mobile and embedded components such as storage, cameras, and radios.
PD Predicate disambiguation gpt-5-mini-2025-08-07 
Target predicate: dataBus
Context triple: [UFS, dataBus, MIPI M‑PHY]
  • A. dataBusType chosen
    Indicates the type or category of data bus used to transfer data between components or systems.
  • B. dataInterface
    Indicates that one entity serves as a data interface through which another entity can access, exchange, or manipulate data.
  • C. systemBus
    Indicates a relationship where a component is connected to or communicates over a shared system-wide communication bus.
  • D. dataPortal
    Indicates that an entity serves as or is associated with an online interface or gateway through which data can be accessed, managed, or distributed.
  • E. dataControl
    Indicates that one entity has the authority or capability to determine how another entity’s data is collected, used, shared, or managed.
  • F. None of above.

Provenance (6 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_69f0a79dfabc81908755382ee47791e2 completed April 28, 2026, 12:27 p.m.
NER Named-entity recognition batch_69f669d648488190b7d3060432eb0eeb completed May 2, 2026, 9:17 p.m.
NED1 Entity disambiguation (via context triple) batch_6a25c1133ad48190bbd371e89b52bc1f completed June 7, 2026, 7:05 p.m.
NEDg Description generation batch_6a25ccabb11c8190b4085aab38ffd0da completed June 7, 2026, 7:55 p.m.
NED2 Entity disambiguation (via description) batch_6a25cd411cd8819082ca2e7fceae0e33 completed June 7, 2026, 7:57 p.m.
PD Predicate disambiguation batch_69f660f4f7a88190b93c60d76b86c912 completed May 2, 2026, 8:39 p.m.
Created at: April 28, 2026, 2:41 p.m.