Triple
T9333604
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Molex |
E224586
|
entity |
| Predicate | componentApplication |
P87567
|
FINISHED |
| Object | personal computers |
—
|
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: personal computers | Statement: [Molex, componentApplication, personal computers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: componentApplication Context triple: [Molex, componentApplication, personal computers]
-
A.
componentAct
Indicates that an action or behavior is performed by a component as part of a larger system or process.
-
B.
component1
Indicates that one entity functions as a constituent or part of another entity within a larger whole.
-
C.
component3
Indicates that one entity is the third component or sub-part within a larger composite structure or system involving another entity.
-
D.
exampleApplication
Indicates that something serves as a representative or illustrative instance of how an application is used or functions.
-
E.
definesApplication
Indicates that one entity specifies or establishes the purpose, scope, or behavior of an application associated with another entity.
- F. None of above. chosen
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_69ca84286fcc81909f6e7fd7a7e862a2 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd37ecfd9481908b54e3d4187fb0ce |
completed | April 1, 2026, 3:21 p.m. |
| PD | Predicate disambiguation | batch_69cc7a643924819097f01144734901cf |
completed | April 1, 2026, 1:52 a.m. |
| PDg | Predicate description generation | batch_69cc94b796788190816b71b1e9996288 |
completed | April 1, 2026, 3:44 a.m. |
Created at: March 30, 2026, 7:39 p.m.