Triple
T18469544
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alexander Osburn |
E451257
|
entity |
| Predicate | hasGivenName |
P17
|
FINISHED |
| Object | Alexander |
—
|
NE NERFINISHED |
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: Alexander | Statement: [Alexander Osburn, hasGivenName, Alexander]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Alexander Context triple: [Alexander Osburn, hasGivenName, Alexander]
-
A.
Alexander
chosen
Alexander is a common male given name of Greek origin, meaning "defender of men."
-
B.
Alexander
Alexander was one of the sons of Herod the Great, a Judean prince whose execution reflected the intense dynastic and political turmoil of Herod’s reign.
-
C.
Alexander
"Alexander" is an epic historical drama film directed by Oliver Stone that chronicles the life and conquests of Alexander the Great.
-
D.
Alexander
Alexander is another name for Paris, the Trojan prince in Greek mythology whose abduction of Helen sparked the Trojan War.
-
E.
Alexander
Alexander is a common surname of Greek origin that has been borne by numerous notable figures across history and culture.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8d38465a0819099b9b42d2a662ac1 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5305e349c8190925166bc3dddb320 |
completed | April 19, 2026, 7:43 p.m. |
Created at: April 10, 2026, 11:34 a.m.