Triple
T14339519
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Martin J. Crowley |
E355556
|
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 J. Crowley, givenName, Martin]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Martin Context triple: [Martin J. Crowley, givenName, Martin]
-
A.
Martin
chosen
Martin is a masculine given name of Latin origin, commonly used in many European languages.
-
B.
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.
-
C.
Martin
Martin is a 1978 American horror film directed by George A. Romero that blends psychological drama and vampire mythology in a gritty, realistic style.
-
D.
Martin
Martin is a renowned brand of acoustic guitars and related instruments produced by C. F. Martin & Company.
-
E.
Martin
Martin is the middle name of Henry Martin Tupper, an individual likely known in historical or biographical records.
- 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_69d8278fa2108190bc0d0e7939c1eb03 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de8e8674c0819091dfbe9c50778c5e |
completed | April 14, 2026, 6:59 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fd469bc538819099ed5b7061cf140d |
completed | May 8, 2026, 2:12 a.m. |
Created at: April 10, 2026, 1:14 a.m.