Triple
T23154693
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Relic |
E578407
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object | NR |
—
|
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: NR | Statement: [New Relic, abbreviation, NR]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: NR Context triple: [New Relic, abbreviation, NR]
-
A.
NR
NR is the standard abbreviation for National Rail, the collective network of passenger railway services in Great Britain.
-
B.
NR
NR is the commonly used abbreviation for the Nordic Council, a regional inter-parliamentary body for cooperation among the Nordic countries.
-
C.
NR
NR is the radio access technology standard defined by 3GPP for fifth-generation (5G) mobile networks, enabling high-speed, low-latency wireless communication.
-
D.
NR
chosen
NR is the common abbreviation for New Relic, a cloud-based observability and application performance monitoring platform used by developers and IT operations teams.
-
E.
NR
NR is the zone code for Northern Railway, one of the major railway zones of Indian Railways headquartered in New Delhi.
- 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_69e245fb8de081908f0eba7b5fd75bc4 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f18efca1f081908ff1c34ba25f40c3 |
completed | April 29, 2026, 4:54 a.m. |
Created at: April 17, 2026, 4:01 p.m.