Triple
T21672328
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LVRN |
E534879
|
entity |
| Predicate | hasAbbreviation |
P43
|
FINISHED |
| Object | LVRN |
—
|
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: LVRN | Statement: [LVRN, hasAbbreviation, LVRN]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: LVRN Context triple: [LVRN, hasAbbreviation, LVRN]
-
A.
LVRN
chosen
LVRN (Love Renaissance) is an Atlanta-based music collective and record label known for managing and developing prominent R&B and hip-hop artists.
-
B.
LVR
LVR is the station code for Lochinvar railway station in New South Wales, Australia.
-
C.
LNV
LNV is the Dutch Ministry responsible for national policies on agriculture, nature conservation, and food quality.
-
D.
VRN
VRN is the public transport association serving Germany’s Rhine-Neckar metropolitan region, coordinating regional and local transit services across multiple states.
-
E.
L.V.O.
L.V.O. is the post-nominal abbreviation for Lieutenant of the Royal Victorian Order, a British order of chivalry recognizing distinguished personal service to the monarch.
- 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_69e0c46898008190aa618a4af55bd1ee |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef8a0cd7648190b9981393f0b2bee9 |
completed | April 27, 2026, 4:08 p.m. |
Created at: April 16, 2026, 6:40 p.m.