Triple
T38596300
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Human Fly |
E934088
|
entity |
| Predicate | hasCultReputationSince |
P170938
|
FINISHED |
| Object | 1980s |
—
|
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: 1980s | Statement: [Human Fly, hasCultReputationSince, 1980s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCultReputationSince Context triple: [Human Fly, hasCultReputationSince, 1980s]
-
A.
hasCultSince
Indicates that an entity has had an organized group of devoted followers (a cult) continuously since a specified time or date.
-
B.
hasCultFollowing
Indicates that something has attracted a small but highly dedicated and enthusiastic group of supporters or fans.
-
C.
hasCultPredecessor
Indicates that one cult, tradition, or religious practice is considered to be derived from, influenced by, or historically preceded by another cult.
-
D.
hasCultOrLegend
chosen
Indicates that an entity is associated with, or is the subject of, a cult, myth, or legendary tradition.
-
E.
timeOfCult
Indicates the specific time or period during which a cult or ritual practice takes place.
- 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_69f76ecc17688190b389b693a5927501 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fec25f0fc48190b87ab1f9cd1eb0de |
completed | May 9, 2026, 5:13 a.m. |
| PD | Predicate disambiguation | batch_69fec079a770819098df7cc3049df954 |
completed | May 9, 2026, 5:04 a.m. |
Created at: May 3, 2026, 4:32 p.m.