Triple
T37469087
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amplitude (2016) |
E931106
|
entity |
| Predicate | hasSimilarGame |
P29155
|
FINISHED |
| Object | Frequency |
—
|
NE NERFINISHED |
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: Frequency | Statement: [Amplitude (2016), hasSimilarGame, Frequency]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSimilarGame Context triple: [Amplitude (2016), hasSimilarGame, Frequency]
-
A.
relatedGame
chosen
Indicates that one game has a notable connection or association with another game, such as shared content, themes, or series.
-
B.
hasGamesAt
Indicates that a particular location, venue, or platform hosts or offers one or more games.
-
C.
associatedWithGame
Indicates that there is a relationship or connection between an entity and a particular game.
-
D.
hasSimilarityTo
Indicates that one entity shares common characteristics, features, or qualities with another entity to a notable degree.
-
E.
hasSimilarCoaster
Indicates that one entity possesses or is associated with a coaster that is similar in characteristics or design to a coaster possessed or associated with another entity.
- 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_69f76ec2af148190897d101070d7f415 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fe72dca2f08190beff17de3d2aada6 |
completed | May 8, 2026, 11:33 p.m. |
| PD | Predicate disambiguation | batch_69fe70bca8d08190b810e1e616ceac44 |
completed | May 8, 2026, 11:24 p.m. |
Created at: May 3, 2026, 4:17 p.m.