Triple
T1612221
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trident layout engine |
E34637
|
entity |
| Predicate | APIs |
P15694
|
FINISHED |
| Object | COM interfaces |
—
|
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: COM interfaces | Statement: [Trident layout engine, APIs, COM interfaces]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: APIs Context triple: [Trident layout engine, APIs, COM interfaces]
-
A.
APIType
chosen
Indicates the type or category of an API associated with or used by an entity.
-
B.
integratesService
Indicates that one entity connects with and enables the functionality of another service so they work together as a unified system.
-
C.
endPoint
Indicates the terminal location, limit, or final state reached by an object, process, or path in a given relationship or action.
-
D.
integratesISP
Indicates that one entity incorporates or connects with an Internet Service Provider (ISP) to enable or enhance network or internet-related functionality.
-
E.
endPointExample
Indicates that something serves as a representative or illustrative instance of a particular endpoint.
- 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_69a885ffc5ec819091afa325d5f9611c |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a93fa6926081908bc78d15c0be3185 |
completed | March 5, 2026, 8:32 a.m. |
| PD | Predicate disambiguation | batch_69a907c35f848190a2428c52e81d013e |
completed | March 5, 2026, 4:34 a.m. |
Created at: March 4, 2026, 7:28 p.m.