Triple

T14538047
Position Surface form Disambiguated ID Type / Status
Subject Sylvanus Apps E341100 entity
Predicate givenName P17 FINISHED
Object Sylvanus E341100 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: Sylvanus | Statement: [Sylvanus Apps, givenName, Sylvanus]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Sylvanus
Context triple: [Sylvanus Apps, givenName, Sylvanus]
  • A. Sylvanus chosen
    Sylvanus is the full given name of Canadian ice hockey legend Syl Apps, a Hall of Fame center known for his career with the Toronto Maple Leafs.
  • B. Médard
    Médard is a masculine French given name of Christian origin, historically associated with Saint Médard and used in various Francophone regions.
  • C. Mahlon
    Mahlon is a minor biblical figure in the Book of Ruth, known as one of Naomi’s sons and the first husband of Ruth.
  • D. Quiney
    Quiney is an English surname historically associated with families in Stratford-upon-Avon, including relatives by marriage of William Shakespeare.
  • E. Artemas
    Artemas is a masculine given name most notably borne by American Revolutionary War general and politician Artemas Ward.
  • 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_69d822dac79c8190a84a073f3cbaced5 completed April 9, 2026, 10:06 p.m.
NER Named-entity recognition batch_69deb1bb90008190947ac0961393446d completed April 14, 2026, 9:29 p.m.
NED1 Entity disambiguation (via context triple) batch_69fd7a5cca788190aa8762d860c78721 completed May 8, 2026, 5:53 a.m.
Created at: April 10, 2026, 1:22 a.m.