Triple
T6850716
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Albert Park Circuit |
E158006
|
entity |
| Predicate | lapRecordCategory |
P30557
|
FINISHED |
| Object | Formula One race lap record |
—
|
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: Formula One race lap record | Statement: [Albert Park Circuit, lapRecordCategory, Formula One race lap record]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lapRecordCategory Context triple: [Albert Park Circuit, lapRecordCategory, Formula One race lap record]
-
A.
registrationCategory
Indicates the classification or type under which an entity is formally registered within a system or registry.
-
B.
F1LapRecordCategory
chosen
Indicates that an entity holds or pertains to a specific category of Formula 1 lap record (such as overall, qualifying, or race lap records).
-
C.
launchRecord
Indicates the act of initiating or starting a recorded instance of a process, event, or operation.
-
D.
notableRecordCategory
Indicates that an entity is notably associated with a particular category of records or record-related achievements.
-
E.
labelCatalog
Indicates assigning or associating a descriptive label or identifier with a catalog entity or catalog entry.
- 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_69c6882fae988190864cbba788c5ebb4 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d84c45708190918adfc028252400 |
completed | March 27, 2026, 7:19 p.m. |
| PD | Predicate disambiguation | batch_69c6d0a12834819097d7e6c0b823745e |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:20 p.m.