Triple
T10433804
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ESV Study Bible |
E245983
|
entity |
| Predicate | hasAbbreviation |
P43
|
FINISHED |
| Object | ESVSB |
E245983
|
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: ESVSB | Statement: [ESV Study Bible, hasAbbreviation, ESVSB]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: ESVSB Context triple: [ESV Study Bible, hasAbbreviation, ESVSB]
-
A.
ESVSB
chosen
ESVSB is the standard abbreviation for the ESV Study Bible, a widely used evangelical Christian study Bible based on the English Standard Version translation.
-
B.
ESV.org
ESV.org is the official online platform for accessing the English Standard Version Bible and its related study resources.
-
C.
ESSV
ESSV is the ICAO airport code for Visby Airport, the main airport serving the island of Gotland in Sweden.
-
D.
Esv
Esv is the official Dutch railway station code used to identify Eindhoven Strijp-S station in the Netherlands.
-
E.
ES-VI
ES-VI is the ISO 3166-2 subdivision code that uniquely identifies the Spanish province of Álava within Spain’s administrative coding system.
- 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_69d381bf3dc08190bf35a2643e4e8f22 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4ea65afe08190b91260c9267a0f14 |
completed | April 7, 2026, 11:28 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d87eb8c70481909b9320af15f2b5e9 |
completed | April 10, 2026, 4:38 a.m. |
Created at: April 6, 2026, 12:14 p.m.