Triple
T17769204
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lancia LC2 |
E443587
|
entity |
| Predicate | designedToCompeteAgainst |
P1375
|
FINISHED |
| Object | Porsche factory Group C cars |
—
|
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: Porsche factory Group C cars | Statement: [Lancia LC2, designedToCompeteAgainst, Porsche factory Group C cars]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designedToCompeteAgainst Context triple: [Lancia LC2, designedToCompeteAgainst, Porsche factory Group C cars]
-
A.
competesWith
chosen
Indicates that two entities are in rivalry or opposition, each striving to outperform or gain advantage over the other in the same domain or objective.
-
B.
designedForCompetition
Indicates that something was intentionally created or configured to be used in a competitive context or event.
-
C.
isCompetitive
Indicates that one entity engages in rivalry or competition with another, typically striving to outperform or win against it.
-
D.
tieneCompetenciaEn
Indicates that an entity possesses skill, expertise, or competence in a specific area, field, or activity.
-
E.
competitionFrom
Indicates that one entity is experiencing competitive pressure or rivalry originating from another entity.
- 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_69d8b9edf16c8190a59ebd245d378f4f |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e485fe70648190b4107e1eabacc694 |
completed | April 19, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69e3d8d8e538819084f1584426b41d5e |
completed | April 18, 2026, 7:17 p.m. |
Created at: April 10, 2026, 10:11 a.m.