Triple
T29143180
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Love and a .45 |
E738691
|
entity |
| Predicate | hasCultStatusSince |
P99775
|
FINISHED |
| Object | late 1990s |
—
|
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: late 1990s | Statement: [Love and a .45, hasCultStatusSince, late 1990s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCultStatusSince Context triple: [Love and a .45, hasCultStatusSince, late 1990s]
-
A.
hasCultSince
chosen
Indicates that an entity has had an organized group of devoted followers (a cult) continuously since a specified time or date.
-
B.
hasSacredStatusSince
Indicates that an entity has held a recognized sacred or holy status starting from a specified point in time.
-
C.
hasAttestedCult
Indicates that an entity is known to have had an established, historically attested cult or formal worship practice.
-
D.
hasCultPredecessor
Indicates that one cult, tradition, or religious practice is considered to be derived from, influenced by, or historically preceded by another cult.
-
E.
hasCultFollowing
Indicates that something has attracted a small but highly dedicated and enthusiastic group of supporters or fans.
- 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_69f07cb3adb48190a9e0e169cd026634 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69fb2e940d5c8190bceae77daf4ef512 |
completed | May 6, 2026, 12:05 p.m. |
| PD | Predicate disambiguation | batch_69f9fec70bd881909c658a3c5020318b |
completed | May 5, 2026, 2:29 p.m. |
Created at: April 28, 2026, 11:38 a.m.