Triple
T7857473
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nvidia Tegra 3 |
E182413
|
entity |
| Predicate | hasCompanionCore |
P79394
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Nvidia Tegra 3, hasCompanionCore, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCompanionCore Context triple: [Nvidia Tegra 3, hasCompanionCore, true]
-
A.
hasCore
Indicates that one entity possesses, contains, or is built around a central or most essential component represented by another entity.
-
B.
hasCompanionPlatform
Indicates that an entity is associated with or supported by an additional platform that accompanies or complements it.
-
C.
hasCompanionCandidate
Indicates that an entity is associated with another entity that is being considered or proposed as a potential companion.
-
D.
hasCompanionPillar
Indicates that an entity is associated with or supported by a corresponding companion pillar.
-
E.
hasCoreUnit
Indicates that an entity includes or is composed around a primary, central, or fundamental unit.
- 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_69ca82887fd48190975896bf38c4596b |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb1a76f8648190976b488d0d8658ef |
completed | March 31, 2026, 12:51 a.m. |
| PD | Predicate disambiguation | batch_69cae925ca388190ae4a01fa76e957e8 |
completed | March 30, 2026, 9:20 p.m. |
| PDg | Predicate description generation | batch_69caf786ec748190b6347b0c94335550 |
completed | March 30, 2026, 10:21 p.m. |
Created at: March 30, 2026, 4:52 p.m.