Triple

T2390514
Position Surface form Disambiguated ID Type / Status
Subject Marc Andreessen E48930 entity
Predicate givenName P17 FINISHED
Object Marc E48930 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: Marc | Statement: [Marc Andreessen, givenName, Marc]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Marc
Context triple: [Marc Andreessen, givenName, Marc]
  • A. Marc chosen
    Marc is the given name of Marc Andreessen, the influential American entrepreneur, software engineer, and venture capitalist known for co-creating the Mosaic web browser and co-founding Netscape and Andreessen Horowitz.
  • B. Marcus
    Marcus is a masculine given name of ancient Roman origin that has been widely used across many cultures and historical periods.
  • C. Markus
    Markus is the given first name of the renowned abstract expressionist painter Mark Rothko.
  • D. Mark
    Mark is a common masculine given name of Latin origin, derived from Marcus and historically associated with figures such as the evangelist Saint Mark.
  • E. Mark
    Mark is the given name of Mark Zuckerberg, the American technology entrepreneur and co-founder of Facebook.
  • 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_69a88aa5f63081908d07fd302029fcbd completed March 4, 2026, 7:40 p.m.
NER Named-entity recognition batch_69abc87457388190822d5506327db8f2 completed March 7, 2026, 6:40 a.m.
NED1 Entity disambiguation (via context triple) batch_69aeb3d4f0608190bcc77a67fa85b963 completed March 9, 2026, 11:49 a.m.
Created at: March 4, 2026, 7:57 p.m.