Triple
T30143819
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CUPRA |
E766196
|
entity |
| Predicate | technologySharingWith |
P54349
|
FINISHED |
| Object | SEAT |
—
|
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: SEAT | Statement: [CUPRA, technologySharingWith, SEAT]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: technologySharingWith Context triple: [CUPRA, technologySharingWith, SEAT]
-
A.
sharesTechnologyWith
chosen
Indicates that one entity provides, exchanges, or jointly uses technology with another entity.
-
B.
sharesPlatformWith
Indicates that two entities operate on, are available through, or participate within the same platform or system.
-
C.
sharesSystemWith
Indicates that two entities operate within or are associated with the same overarching system or environment.
-
D.
sharesFeatureWith
Indicates that two entities have at least one common attribute, property, or characteristic in common.
-
E.
sharesUniverseWith
Indicates that two entities exist within the same fictional or narrative universe, implying shared continuity, setting, or canon.
- 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_69f2247909048190ae86c2160cf8b566 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68f670b608190a0b6ab60d722b4e0 |
completed | May 2, 2026, 11:57 p.m. |
| PD | Predicate disambiguation | batch_69f68b7b03488190b1db5fde4c7dd6e5 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 29, 2026, 7:18 p.m.