Triple
T15840404
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Group A touring cars |
E384085
|
entity |
| Predicate | governedAspect |
P31808
|
FINISHED |
| Object | minimum weight |
—
|
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: minimum weight | Statement: [Group A touring cars, governedAspect, minimum weight]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governedAspect Context triple: [Group A touring cars, governedAspect, minimum weight]
-
A.
governsAspectOf
chosen
Indicates that one entity exercises control, regulation, or determining influence over a particular aspect or component of another entity.
-
B.
governedAs
Indicates that one entity exercises authoritative control, direction, or rule over another according to some system of governance or leadership.
-
C.
onAspect
Indicates that one entity is positioned on a particular side, surface, or facet of another entity.
-
D.
governedThrough
Indicates that one entity exercises control, authority, or administration over another entity by means of a specified intermediary mechanism, structure, or process.
-
E.
governedWith
Indicates that two or more entities share or participate together in the act or process of governing.
- 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_69d86da34c888190976e06c4019d415a |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e142e69360819091ea0556bd66d785 |
completed | April 16, 2026, 8:13 p.m. |
| PD | Predicate disambiguation | batch_69e005418f588190824d91ff7974dada |
completed | April 15, 2026, 9:38 p.m. |
Created at: April 10, 2026, 4:49 a.m.