Triple

T15906229
Position Surface form Disambiguated ID Type / Status
Subject Ampersand E385726 entity
Predicate associatedWithCharacter P1481 FINISHED
Object Agent 355 E385727 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: Agent 355 | Statement: [Ampersand, associatedWithCharacter, Agent 355]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Agent 355
Context triple: [Ampersand, associatedWithCharacter, Agent 355]
  • A. Agent 355 chosen
    Agent 355 is a skilled and enigmatic covert operative from the Culper Ring who serves as Yorick Brown’s protector in the post-apocalyptic comic series "Y: The Last Man."
  • B. Agent 326
    Agent 326 is a fictional spy character known for undertaking covert missions and espionage activities.
  • C. Agent 13
    Agent 13 is the covert alias used by James Wilkinson, a character known as a skilled undercover operative in the Marvel universe.
  • D. Agent 13
    Agent 13 is the codename of Sharon Carter, a highly skilled S.H.I.E.L.D. operative and frequent ally of Captain America in Marvel Comics.
  • E. Agent 13
    Agent 13 is an unproduced film script centered on a mysterious spy character, known primarily within industry and fan circles for its unrealized cinematic potential.
  • 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_69d86da686e4819097cbf3b1fc2d881d completed April 10, 2026, 3:25 a.m.
NER Named-entity recognition batch_69e1565b0d688190acc181c777387c65 completed April 16, 2026, 9:36 p.m.
NED1 Entity disambiguation (via context triple) batch_69ffb5a5b0dc81909606d667c3bc0edf completed May 9, 2026, 10:31 p.m.
Created at: April 10, 2026, 4:52 a.m.