Triple
T27606617
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Southern California car culture |
E700196
|
entity |
| Predicate | hasAssociatedEventType |
P38977
|
FINISHED |
| Object | cruise night |
—
|
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: cruise night | Statement: [Southern California car culture, hasAssociatedEventType, cruise night]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAssociatedEventType Context triple: [Southern California car culture, hasAssociatedEventType, cruise night]
-
A.
hasEventType
Indicates that an event is associated with, or classified under, a specific type or category of event.
-
B.
associatedEventType
chosen
Indicates that one entity is linked to another by the type or category of event with which it is associated.
-
C.
hasAssociatedType
Indicates that one entity is linked to another entity that specifies its type, category, or classification.
-
D.
refersToEventType
Indicates that one entity references or is associated with a specific type or category of event.
-
E.
appearsAtEventType
Indicates that an entity is present or participates in an event of a specified type.
- 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_69ef6a4e2e208190b63b7268f405785c |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f6a28c7c148190bfc980aad9f678ca |
completed | May 3, 2026, 1:19 a.m. |
| PD | Predicate disambiguation | batch_69f69fe1e3c88190830bb2e9f407357e |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 27, 2026, 2:10 p.m.