Triple
T10030804
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bright Eyes |
E204845
|
entity |
| Predicate | notableSong |
P4
|
FINISHED |
| Object | Lua |
E750191
|
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: Lua | Statement: [Bright Eyes, notableSong, Lua]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lua Context triple: [Bright Eyes, notableSong, Lua]
-
A.
Lua
Lua is a lightweight, embeddable scripting language widely used for game development, configuration, and extending applications.
-
B.
Lua
chosen
"Lua" is a folk-influenced song by Bright Eyes, known for its stark, intimate portrayal of loneliness and addiction.
-
C.
Lua
Lua is a minor Roman goddess associated with the protection and ritual destruction of captured enemy weapons and spoils of war.
-
D.
LUA
LUA is the IATA airport code for Tenzing-Hillary Airport, the small but famous gateway to Nepal’s Everest region.
-
E.
LuaJIT
LuaJIT is a high-performance just-in-time compiler and runtime for the Lua programming language, designed to provide significantly faster execution while maintaining compatibility with standard Lua.
- 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_69ca834d77188190ad645e33e8ca3200 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cdcde7ec088190845656cc2529c771 |
completed | April 2, 2026, 2:01 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d2823e63488190bef7633b1a755df8 |
completed | April 5, 2026, 3:39 p.m. |
Created at: March 30, 2026, 8:54 p.m.