Triple

T9892890
Position Surface form Disambiguated ID Type / Status
Subject ByteDance E181496 entity
Predicate product P490 FINISHED
Object Resso E828496 NE 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: Resso | Statement: [ByteDance, product, Resso]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Resso
Context triple: [ByteDance, product, Resso]
  • A. Resso chosen
    Resso is a music streaming app known for its social and interactive features, developed by TikTok parent company ByteDance.
  • B. Guapira
    Guapira is a genus of flowering plants in the four o'clock family, comprising mostly tropical American trees and shrubs.
  • C. Noresco
    Noresco is an energy services and performance contracting company known for developing and implementing energy efficiency and infrastructure modernization projects.
  • D. Lusei
    Lusei are a major clan of the Mizo people of Northeast India, historically influential in shaping Mizo culture, language, and social organization.
  • E. Funka
    Funka is a small village in northern Poland known for its scenic lakeside setting and recreational access to Lake Charzykowskie.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69ca8283a6708190801af7a25a7ebb9f completed March 30, 2026, 2:02 p.m.
NER Named-entity recognition batch_69cdb4814a3c8190ab1fd7f755a44508 completed April 2, 2026, 12:12 a.m.
NED1 Entity disambiguation (via context triple) batch_69d20d888b408190a68ff55d63558478 completed April 5, 2026, 7:21 a.m.
Created at: March 30, 2026, 8:39 p.m.