Triple

T25532184
Position Surface form Disambiguated ID Type / Status
Subject McAvoy E639948 entity
Predicate hasNotableBearer P458 FINISHED
Object Jim McAvoy
Jim McAvoy is a relatively obscure individual whose primary distinguishing feature is sharing the McAvoy surname, rather than being widely recognized for notable public achievements.
E1687370 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: Jim McAvoy | Statement: [McAvoy, hasNotableBearer, Jim McAvoy]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Jim McAvoy
Triple: [McAvoy, hasNotableBearer, Jim McAvoy]
Generated description
Jim McAvoy is a relatively obscure individual whose primary distinguishing feature is sharing the McAvoy surname, rather than being widely recognized for notable public achievements.

Provenance (5 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_69e75dbf3f9c8190b3f2a75d1b75d127 completed April 21, 2026, 11:21 a.m.
NER Named-entity recognition batch_69f5f863b97481908c64be433f36980e completed May 2, 2026, 1:13 p.m.
NED1 Entity disambiguation (via context triple) batch_6a10b749dc74819083698f357169e1ce completed May 22, 2026, 8:06 p.m.
NEDg Description generation batch_6a10b84949448190ba06c85d0f19215b completed May 22, 2026, 8:10 p.m.
NED2 Entity disambiguation (via description) batch_6a10b9606818819094491a74c5922378 completed May 22, 2026, 8:15 p.m.
Created at: April 21, 2026, 3:15 p.m.