Triple
T6623320
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fiat 124 Abarth Rally |
E149729
|
entity |
| Predicate | homologationPurpose |
P56768
|
FINISHED |
| Object | international rally competition |
—
|
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: international rally competition | Statement: [Fiat 124 Abarth Rally, homologationPurpose, international rally competition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homologationPurpose Context triple: [Fiat 124 Abarth Rally, homologationPurpose, international rally competition]
-
A.
homologationFor
chosen
Indicates that something is formally approved, certified, or validated for a specific use, standard, or regulatory context.
-
B.
homologationRequirement
Indicates that an entity is subject to a formal approval or certification process that must be completed before it can be legally accepted, used, or marketed.
-
C.
reasonForUse
Indicates that one entity specifies the justification, purpose, or motivation for using another entity.
-
D.
encodingPurpose
Indicates the reason or intended use for which an encoding is created or applied.
-
E.
designationUsedFor
Indicates that a particular name, label, or title is employed to refer to or identify a specific entity or role.
- 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_69c687ed8a9c81908bb671717cb192ef |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6bdb88cc881908f35648c15a7dc85 |
completed | March 27, 2026, 5:26 p.m. |
| PD | Predicate disambiguation | batch_69c6ad007c1c8190af425f51011c7ad1 |
completed | March 27, 2026, 4:14 p.m. |
Created at: March 27, 2026, 1:58 p.m.