Triple
T35917565
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rally4 |
E1038788
|
entity |
| Predicate | homologationRequired |
P56218
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Rally4, homologationRequired, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homologationRequired Context triple: [Rally4, homologationRequired, yes]
-
A.
homologationRequirement
chosen
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.
-
B.
homologationFor
Indicates that something is formally approved, certified, or validated for a specific use, standard, or regulatory context.
-
C.
homologationBasis
Indicates the underlying standard, criteria, or reference used as the basis for officially approving or certifying something through homologation.
-
D.
homologationBody
Indicates the organization or authority responsible for officially approving or certifying something (such as a product, process, or standard) for compliance or use.
-
E.
homologationClass
Indicates the specific regulatory or competitive category under which something (typically a vehicle or product) has been officially approved or certified.
- 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_69f76e2320748190b7f5c4750d0cd0d3 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7ac23d1388190bdf9628b294943bd |
completed | May 3, 2026, 8:12 p.m. |
| PD | Predicate disambiguation | batch_69f7ab734d848190a84f9b8c3a952b75 |
completed | May 3, 2026, 8:09 p.m. |
Created at: May 3, 2026, 4:07 p.m.