Triple
T29858622
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GeForce 256 |
E758255
|
entity |
| Predicate | boardPartners |
P34923
|
FINISHED |
| Object | ASUS |
—
|
NE NERFINISHED |
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: ASUS | Statement: [GeForce 256, boardPartners, ASUS]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: boardPartners Context triple: [GeForce 256, boardPartners, ASUS]
-
A.
exportPartners
Indicates a relationship where one entity collaborates with or serves as a partner to another in exporting goods or services across borders.
-
B.
primaryPartners
Indicates that the entities are each other’s main or most significant partners in a relationship, typically implying priority or exclusivity over other partnerships.
-
C.
cooperationPartner
chosen
Indicates that two entities are engaged in a collaborative relationship, working together toward shared goals or mutual benefit.
-
D.
partnerNation
Indicates that one entity is recognized as a collaborating or allied nation in relation to another entity.
-
E.
projectPartners
Indicates that two or more entities collaborate together as partners on the same project.
- 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_69f2245b4dec8190b85f664d918a00a5 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f6768345fc8190bdc72aa7af054375 |
completed | May 2, 2026, 10:11 p.m. |
| PD | Predicate disambiguation | batch_69f66ac32b60819092290b2de35988d3 |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 29, 2026, 5:47 p.m.