Triple
T1428492
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mitchell Kapor |
E30388
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Kapor |
E34845
|
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: Kapor | Statement: [Mitchell Kapor, familyName, Kapor]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kapor Context triple: [Mitchell Kapor, familyName, Kapor]
-
A.
Kapor
chosen
Kapor is the surname of Mitchell Kapor, an American entrepreneur best known for founding the software company Lotus Development Corporation.
-
B.
Kierling
Kierling is a small locality in Lower Austria best known as the place where writer Franz Kafka spent his final days and died.
-
C.
Sokar
Sokar is an ancient Egyptian funerary god associated with the Memphite necropolis, the afterlife, and aspects of death and rebirth.
-
D.
Pekar
Pekar is a surname of Central or Eastern European origin, notably associated with several cultural and artistic figures.
-
E.
Karmanor
Karmanor is a minor figure in Greek mythology known as a Cretan hero or priest associated with the goddess Demeter.
- 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_69a498fb823c8190a67ce4c4837e641a |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c4d9575881908bb58598e5a80590 |
completed | March 1, 2026, 10:59 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ad016930ec8190ab3900d6f40c4aa0 |
completed | March 8, 2026, 4:56 a.m. |
Created at: March 1, 2026, 8 p.m.