Triple
T14636678
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adam Patch |
E343624
|
entity |
| Predicate | hasFamilyName |
P18
|
FINISHED |
| Object | Patch |
E175801
|
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: Patch | Statement: [Adam Patch, hasFamilyName, Patch]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Patch Context triple: [Adam Patch, hasFamilyName, Patch]
-
A.
Patch
chosen
Patch is a surname most notably associated with Alexander Patch, a senior U.S. Army general who played a key role in World War II operations in Europe.
-
B.
Patch
Patch is one of the Dalmatian puppies from Disney's "101 Dalmatians," recognizable by his distinctive black ear and energetic, adventurous personality.
-
C.
Patching
Patching is a small rural village and civil parish in West Sussex, England, situated within the South Downs and known for its scenic countryside and historic church.
-
D.
Fix
Fix is a surname most notably associated with American character actor Paul Fix, known for his extensive work in Western films and television.
-
E.
Fixem
Fixem is a small commune in northeastern France, situated within the Moselle department in the Grand Est region.
- 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_69d822dffc3c8190aa173b90761bffda |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb4ab9578819085b4cf7244d30d87 |
completed | April 14, 2026, 9:42 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fda934ec3c81909eb3c3a54260436b |
completed | May 8, 2026, 9:13 a.m. |
Created at: April 10, 2026, 1:26 a.m.