Triple
T10376226
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Martin Perl |
E244514
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Martin |
E223140
|
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: Martin | Statement: [Martin Perl, givenName, Martin]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Martin Context triple: [Martin Perl, givenName, Martin]
-
A.
Martin
Martin is a minor but kind-hearted character in Ernest Hemingway's novella "The Old Man and the Sea," known for helping the old fisherman Santiago.
-
B.
Martin
Martin is a common surname of European origin, widely borne by individuals across many countries and cultures.
-
C.
Martin
chosen
Martin is a masculine given name of Latin origin, commonly used in many European languages.
-
D.
Martin
Martin was the given name of Martin I of Aragon, a medieval king who ruled the Crown of Aragon at the turn of the 15th century.
-
E.
Martin
Martin is a character in Don DeLillo’s novel "Falling Man," which explores the personal and psychological aftermath of the September 11 attacks.
- 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_69d381b3e328819094b23b8edcd29b5a |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4e98278e08190a4d3ff88b4039e49 |
completed | April 7, 2026, 11:24 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d795754570819093747f80e32fffce |
completed | April 9, 2026, 12:03 p.m. |
Created at: April 6, 2026, 12:02 p.m.