Triple
T11997070
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House of Montague |
E285558
|
entity |
| Predicate | hasMember |
P10
|
FINISHED |
| Object | Balthasar |
E561804
|
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: Balthasar | Statement: [House of Montague, hasMember, Balthasar]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Balthasar Context triple: [House of Montague, hasMember, Balthasar]
-
A.
Balthasar
chosen
Balthasar is a given name of biblical origin traditionally associated with one of the Three Wise Men in Christian tradition.
-
B.
Melchior
Melchior is traditionally known as one of the Three Wise Men or Magi who visited the infant Jesus, often depicted as an aged king bearing gifts.
-
C.
Baltasar
Baltasar is a variant of the name Belshazzar, historically associated with the last king of Babylon mentioned in the biblical Book of Daniel.
-
D.
Sindorf
Sindorf is a district of the town of Kerpen in North Rhine-Westphalia, Germany.
-
E.
Baldassarre
Baldassarre is an Italian surname of likely patronymic or given-name origin, borne by various notable individuals in Italy.
- 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_69d6ab44a77c8190a652f4b27164e4ef |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d903c172788190b92042e9d10a48bf |
completed | April 10, 2026, 2:05 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f47281ea7c819081921bc125f8895f |
completed | May 1, 2026, 9:29 a.m. |
Created at: April 8, 2026, 9:46 p.m.