Triple
T8917072
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lord of Babylon |
E212318
|
entity |
| Predicate | relatedTitleOfSameDeity |
P46701
|
FINISHED |
| Object | Bel |
E132022
|
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: Bel | Statement: [Lord of Babylon, relatedTitleOfSameDeity, Bel]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bel Context triple: [Lord of Babylon, relatedTitleOfSameDeity, Bel]
-
A.
Bel
chosen
Bel is a major Mesopotamian god, often identified with Marduk, revered as a supreme deity and lord of the heavens and earth in Babylonian religion.
-
B.
Bal
Bal is the given name of Bal Gangadhar Tilak, a prominent Indian nationalist leader and social reformer of the late 19th and early 20th centuries.
-
C.
BEL
BEL is the ICAO airline designator used to identify Brussels Airlines in international aviation operations.
-
D.
BEL
BEL is the three-letter ISO 3166-1 alpha-3 country code that uniquely identifies Belgium in international standards and data systems.
-
E.
BEL
BEL is the commonly used abbreviation for Bharat Electronics Limited, an Indian state-owned aerospace and defense electronics company.
- 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_69ca8393b1808190bd4336787ffa2c40 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6610cd48819090a184c5f9465626 |
completed | April 1, 2026, 12:25 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cfba4567a88190855b964bc6e3ac6f |
completed | April 3, 2026, 1:01 p.m. |
Created at: March 30, 2026, 6:56 p.m.