Triple
T35164015
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | F4 UAE |
E1015344
|
entity |
| Predicate | regulationCategory |
P148432
|
FINISHED |
| Object | FIA Formula 4 |
—
|
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: FIA Formula 4 | Statement: [F4 UAE, regulationCategory, FIA Formula 4]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regulationCategory Context triple: [F4 UAE, regulationCategory, FIA Formula 4]
-
A.
categoryForRegulation
chosen
Indicates that something is assigned to a specific regulatory category or classification for the purposes of applying rules or controls.
-
B.
regulatoryType
Indicates the specific kind or category of regulatory control, rule, or oversight that applies in the given relationship.
-
C.
regulationAtIssue
Indicates that a specific regulation is the subject of concern, dispute, or analysis in the given context.
-
D.
regulatedIn
Indicates that one entity’s activity, expression, or occurrence is controlled, influenced, or modulated by another entity within a specific context or system.
-
E.
subjectToRegulation
Indicates that an entity is governed, constrained, or controlled by a specific rule, law, or regulatory framework.
- 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_69f76ddbfde081908bffc91572368289 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fd82ed2a4c81908bd7797fbd2e3d08 |
completed | May 8, 2026, 6:30 a.m. |
| PD | Predicate disambiguation | batch_69fd814cc10481908e4f8123d35a5d0c |
completed | May 8, 2026, 6:23 a.m. |
Created at: May 3, 2026, 4:02 p.m.